dbt Boundary Cheat Sheet
Recall when to use source, ref, and layer-specific tests.
Recall What is the boundary rule of thumb? Make the dependency explicit, keep one responsibility per layer, and add a test for the assumption people rely on. This turns model code into a reviewable contract. Objection It runs fine if I hard-code the table name. Say this Running is not the same as being managed by dbt. Use source() or ref() so lineage, environments, and selection work. Arguing style preference instead of explaining dependency visibility. It reframes the rule around operational safety. Compare Which boundary is this? The boundary determines ownership and lineage. Checklist GUT What is the GUT check…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in