Recap and next steps

Keep the habits, not the template

This course built six habits: resolve ambiguity before SQL; write a contract two analysts would implement identically; profile before modeling; annotate grain to expose fan-out; write descriptions for observed failures; and measure whether context helped.

They survive a warehouse change, a model change, or a move to dbt, Dataform, SQLMesh, or an in-house platform because they are checks and decisions rather than product syntax. The advanced course adds pipelines, tests, incremental loads, and operating the work with an agent without giving it production access.

Your task

In the conversation, name one habit you will use on a specific piece of work in the next week. Name the course number that changed how you think about trusting a query, and explain why it surprised you.

Check your understanding

• Name the six habits, in the order the course taught them.
• Why is habit six the one most likely to get skipped, and why does that matter?
• What does the advanced course add that this one deliberately left out?

Do it with your agent

Say next lesson, give your real-work answer, then say review my work. The agent should check that the habit, work, number, and reason are all concrete.

Next steps

Apply the contract and profiling routine to a live model before your next change. Then move into the advanced course when you need tests, incremental work, and production operating practices.