↓ Skip to main content

dbt

dbt is the link between the transformation code and the decisions a data team has to maintain: how models are tested, what columns mean, and which rules are enforced before deployment.

Start with treating transformations as infrastructure, then documentation and governance. For an example of the tooling around those checks, see dbt-guard. The posts below describe the choices, limits and implementation details.

dbt Data Tests in YAML: Stop Praying Your Data Is Correct

dbt Data Tests in YAML: Stop Praying Your Data Is Correct

··1601 words·8 mins
A report spits out weird numbers. An analyst tells you “the totals don’t match,” and you spend your day tracing back up the chain. The habit I keep coming back to is boring: dbt data tests, declared in YAML beside the columns, and actually run in CI. Tell the pipeline what you expect before a dashboard tells you what went wrong.
dbt Documentation: YAML, persist_docs and Governance

dbt Documentation: YAML, persist_docs and Governance

··1392 words·7 mins
In my dbt projects, YAML is where descriptions, tests and ownership live together. I use persist_docs to carry model descriptions into Snowflake, then CI checks to stop the documentation quietly falling behind. The governance part comes from what we build around that metadata. It doesn’t happen because a file happens to be YAML.