New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
9 recipes Β· 60 steps Β· about 42 minutes of reading
One SQL query, pulling straight from the raw orders table. Three other reports are already asking to copy it.
I ran a dbt model against what I thought was my sandbox. It rebuilt three tables our dashboard reads from.
A join between orders and customers is dropping rows, and nobody noticed until finance asked why the numbers didn't add up.
The same currency-conversion CASE statement is pasted into six models, and I just fixed a bug in one copy without touching the other five.
None of the four built-in tests catches a completed order with a negative total. Finance just found one.
dbt run just failed: Found a cycle. No idea which two models are pointing at each other.
Someone wants to rename a column. What breaks downstream if they do?
The nightly job that rebuilds the whole orders table now takes ninety minutes, and the warehouse bill has three people asking questions.
A broken model made it to production last week, and the first anyone heard about it was a Slack message from the CEO's dashboard.
Cookbook badge
Finish all 9 recipes to earn this.