Code Review

Beginner · Roadmap · 6 lessons · 1 groups

The craft of peer review itself — not the design judgment a reviewer applies (that's `software-design-architecture`/`software-architect`), but the practice around it: why review earns its cost, preparing a change so it's actually reviewable, what a reviewer should spend attention on, the etiquette of giving and receiving feedback without it turning adversarial, pushing the mechanical checks onto tools instead of people, and the failure modes (bikeshedding, rubber-stamping, review fatigue) that show up once a team does this every day.

0%

Not started

Nothing saved yet. Progress is kept in this browser until you sign in.

Start the path
Esc
↑↓ navigate↵ open? shortcuts

Keyboard shortcuts

Press Esc to close

Anywhere

⌘K
Search and commands
/
Search
?
This sheet
Esc
Close

Reading a lesson

J
Next lesson
K
Previous lesson
B
Bookmark