Professional developers spend more time reading code than writing it — yet beginners practise almost only writing. Flip that ratio early and everything gets easier: debugging, tutorials, even job interviews.

1. Narrate before you run

Open any short program and predict, line by line, what it does — out loud. Then run it. The gap between prediction and reality is precisely where learning lives.

2. Keep a bug journal

Every error you meet gets one line: what it said, what it meant, what fixed it. Within a month your journal answers half your questions before you ask them.

3. Steal structure, not code

When a tutorial solution works, rebuild it from memory with different variable names and values. If you can, you understand it; if you cannot, you have found your next lesson.

Our Computer Sciences track practises all three habits from lesson one. Bring curiosity — we will supply the errors, kindly explained.