<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Governance on Damien GOEHRIG</title><link>https://damiengoehrig.ca/tags/data-governance/</link><description>Recent content in Data Governance on Damien GOEHRIG</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Damien GOEHRIG</copyright><lastBuildDate>Fri, 16 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://damiengoehrig.ca/tags/data-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>dbt: When Your YAML Files Become Your Data Governance</title><link>https://damiengoehrig.ca/blog/dbt-documentation-governance-yml/</link><pubDate>Fri, 16 Jan 2026 00:00:00 +0000</pubDate><guid>https://damiengoehrig.ca/blog/dbt-documentation-governance-yml/</guid><description>&lt;p&gt;Documentation is the thing nobody wants to do. Especially in data. You have hundreds of columns across dozens of tables, and someone asks &amp;ldquo;what&amp;rsquo;s the &lt;code&gt;status&lt;/code&gt; field in the &lt;code&gt;orders&lt;/code&gt; table?&amp;rdquo; And the honest answer is often &amp;ldquo;uh&amp;hellip; an enum I think that probably means X.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>