← Previous · Film 5 of 10
Promises and proofs
Every gap gets a decision. Promise it in a contract; prove it with a test, written before the code it checks.
Topics › Analytics engineering › In the weeds of data crafting
The tests are written, and they wait for code. Like the stations of Escoffier's kitchen, each layer of Jun's project does one job: staging tidies a table, intermediate holds the steps, the core holds what the blueprint names, and each mart serves one consumer. Inside a model, each CTE is one step.
Builds on Promises and proofs
Press Play, or pick a chapter. Turn on Pause and think to stop for one question at the end of chapters.

Download the videoCaption filesRead the script
Where next?
Every card in the film shows a real file from the example dbt project. Open the ones each chapter shows, on GitHub, or run the whole project yourself.
skills/draft-a-model/SKILL.md models/staging/short_courses/stg_short_courses__learners.sql docs/conventions.mddocs/conventions.md models/intermediate/student/int_learner_timeline.sqldbt_project.yml models/core/course/core_award.sqlmodels/marts/wallet/_wallet__models.ymlmodels/marts/planning/mart_planning__near_award.sql docs/conventions.mddbt_project.yml models/core/student/core_credential_v2.sqlmacros/planning/near_award.sql dbt_project.yml models/marts/planning/_planning__semantic.ymlThe four Pause and think questions, for a class or a team. Open one to see the answer.
Film 6 of 10.
← Previous · Film 5 of 10
Every gap gets a decision. Promise it in a contract; prove it with a test, written before the code it checks.
Next · Film 7 of 10 →
Each fact's meaning has an owner. Owners publish a public, versioned core; consumers build on it, never on each other's marts.