Five minutes at the door, every class. None of these routines needs a computer and none of them is filler — each one drills a single habit that programming will later demand at full speed. Reading code closely, naming a fault precisely, asking the question that saves an hour of building the wrong thing: these are not talents, they are reps.
| Warm-up | What it trains |
|---|---|
| Predict the Output | Reading code closely enough to commit |
| Spot the Bug | Finding faults by reading, not by re-running |
| Trace It | Following a program the way Python does, line by line |
| Which One Doesn’t Belong | Precise vocabulary, defended out loud |
| Name That Error | Turning a traceback into a diagnosis |
| Tech Headlines | Weighing claims made about technology |
| What Would You Ask | The question that comes before the code |
Six of these point at the machine. The seventh points at a person: What Would You Ask is where you practise the interview that The Community App eventually depends on, one question at a time, long before there is anything to build.
If a round ever feels pointless, check the right-hand column and watch for that one thing next time. The tenth round is never the first.