Every coding colab and every end-of-day practice exercise has a key. The keys are published from the start of the course, so you can check your work the same evening you do it.
Work the exercise first, then come here. A key you read before you try the problem teaches you very little, because reading working code feels much easier than writing it.
The code in a key is one correct answer, not the only one. If your code looks different but produces the same numbers, you were right.
The written answers matter more than the code. You can already tell whether your code ran. What you cannot check on your own is whether you read the result correctly, and that is what the green Answer boxes are for. Compare them against your own markdown cells, and pay attention to the difference between stating a number and reading it.
π Coding colabs
The Day 2 colab, Five Claims About a Dataset Youβve Never Seen, has no key on purpose. You choose which five claims to make, so there is no fixed set of numbers to check yours against. Bring your claims to the Day 3 morning session instead.
π End-of-day practice
Days 8 and 9 have no keys, because you build your own project rather than work a set exercise. See the final project for what is expected there.
What a good written answer looks like
Each key closes with a short list called Where the marks are, naming the three or four things most worth checking in that exercise. One item appears in every list, so it is worth stating here as well.
An answer should say what a number means, not what it is. β34 foods score above 10β repeats the output. β34 foods, a fifth of the dataset, and almost all of them meat or hard cheeseβ reads it. The second sentence is the one that shows you understood the result, and it is the habit the keys are trying to build.