One review a week. You bring working code, and the group reads it for truthfulness: states, failures, and names.
A build on your own clock. The next review starts from what you pushed, including the part that is still rough.
- 01
Three jobs
Interface, API, and data, and why mixing them makes a mess.
- 02
States that tell the truth
Loading, empty, and failure as part of the interface.
- 03
A small API
Errors designed on purpose, not discovered by a user.
- 04
Saving work
The cases that lose or double a write.
- 05
Reading other people's code
How to enter a codebase without narrating around it.
- 06
Review and done
Tests, notes, and a definition of finished you can keep.
- 07
A tool you can demo
Something small enough to show without apologizing for the path.