Becoming a Code Reader
You cannot verify what you cannot read. This month builds the skill that makes everything else possible: reading code as the computer executes it, tracing state, finding bugs, and reviewing other minds' work.
The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility.
Time commitment
Each week pairs a short reading (~30-60 min) with substantial practice (5-10 hours). Budget 6-7 hours per week total. The practice is where the learning happens.
~3 hours reading
4 lessons total
~23 hours practice
49 exercises + capstone
Weekly breakdown
Week 1: State Tracing
Week 2: Bug Hunting
Week 3: Code Explanation
I learned very early the difference between knowing the name of something and knowing something.
Ready to start?
Each week has three parts: read the lesson, observe the Fishbowl, then practice the exercises. Reading builds the mental model. Observing shows it in action. Practice makes it stick.