Recap and next steps

What you completed

You built a set of habits, not only a set of queries:

• Read a query before trusting its output.
• Name what one row represents before writing or accepting SQL.
• Check every join for fan-out.
• Verify a headline number with a second, independent method.
• Keep a short list of anchor numbers and reconcile against it.
• Write a correction into the repository, not only into the next prompt.

If you want to keep practising at a bigger scale, the project README's "Working at a bigger scale" section lists three paths, from a 6-million-row generated benchmark to connecting your own warehouse.

Keep the workflow

The loop you practised - ask, read, interrogate, verify, accept or reject - is not a beginner scaffold you outgrow. It is how experienced people work with SQL they did not write, whether the author is an agent or a colleague. The dataset was small so you could check every total by hand. On a real warehouse the totals are too large to eyeball, which is exactly when the loop earns its keep.

The next course, Design the Model, turns the question around: instead of auditing a query someone handed you, you design the query and the model behind it, and you make the repository something an agent can reason about well enough to get more right on the first try.

Next steps

• Design the Model - the intermediate course, shown on the programme overview.
• Bruin documentation - the reference for bruin query and every other command.
• Data quality checks - turn a caught mistake into a check that catches it next time.
• Join the Bruin community on Slack - ask questions about the material or your own data.