Code Review
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.
Why Code Review MattersWhat code review actually catches — shared ownership, consistency, and surfaced alternatives — and the failures it's realistically bad at finding.Writing a Reviewable Pull RequestHow to size, self-review, and describe a pull request so a reviewer can actually hold the change in their head.What Reviewers Look ForA priority order for code review — design and correctness first, then tests and readability, with style left to the linter.Giving and Receiving FeedbackHow to phrase review comments without softening the substance, and how to read them without taking them personally.Automating the Easy ChecksWhy formatting and style debates are the wrong place for a reviewer's attention, and how linters, formatters, and CI gates take that work off the table.Common Code Review PitfallsThe recurring ways daily code review breaks down — bikeshedding, rubber-stamping, bottleneck reviewers, scope creep — and the structural fix for each.
The practice of review
- Why Code Review MattersWhat code review actually catches — shared ownership, consistency, and surfaced alternatives — and the failures it's realistically bad at finding.
- Writing a Reviewable Pull RequestHow to size, self-review, and describe a pull request so a reviewer can actually hold the change in their head.
- What Reviewers Look ForA priority order for code review — design and correctness first, then tests and readability, with style left to the linter.
- Giving and Receiving FeedbackHow to phrase review comments without softening the substance, and how to read them without taking them personally.
- Automating the Easy ChecksWhy formatting and style debates are the wrong place for a reviewer's attention, and how linters, formatters, and CI gates take that work off the table.
- Common Code Review PitfallsThe recurring ways daily code review breaks down — bikeshedding, rubber-stamping, bottleneck reviewers, scope creep — and the structural fix for each.