Task fit
What was the original task, and does the code implement a reasonable approach?
weekly read code lab
A new code-reading exercise every week.
The goal is to learn to read code like a reviewer. Each week has a diff, a task brief, and questions that help you decide whether the code meets the requirements, preserves old behavior, uses clean abstractions, and has enough testing evidence.
review checklist
Questions to ask while reading a diff
Regression risk
If this is not net-new logic with clear boundaries, are previous requirements still satisfied?
Abstractions
Are new functions appropriately scoped, or did modified functions become too busy?
Unit tests
Is the business logic covered by focused unit tests, especially important edge cases?
Staging evidence
Did the author provide reasonable evidence from staging, pseudo-production, or manual checks?
Code quality
Is the code logical, readable, error-free, maintainable, and safe enough to approve?
archive
Weekly labs
The archive is powered by /data/read-code-labs.json, so one new exercise can be added each week without changing the page structure.