Give code reviews that improve the code without crushing the author. Receive reviews without defensiveness. Tag severity. Know when to convert a thread to a call. Review strangers' contributions in a way that brings them back. In a convention-strong ecosystem, review attention goes to deviations — the conventional thing needs no comment; the unconventional thing needs justification. That's a sharper bar than "this is suboptimal," and it's why a missing linter config masquerades as a code-review problem: if humans are commenting on quote styles, fix the upstream cause and reclaim the human review for human judgment. Watch also for what the diff doesn't show — callbacks, hooks, and framework magic that change what a small diff actually does; "what does this trigger downstream?" is the question that distinguishes reviewers who read diffs from reviewers who read systems. And remember the medium's physics: a review comment is a permanent, public, line-anchored payload with no tone channel. Engineer accordingly.
This course unlocks once you've finished its prerequisite. Open prerequisite →
Code review is the only writing form where you see your impact on a real person fast. You leave a comment; you get a reply within thirty minutes; you can tell instantly whether it…
Code review is the only form of text-based critique most engineers practice with regularity — you both give and receive, weekly, in a stripped-down medium that is permanent, searc…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Three exercises, ~30 minutes each:
9 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.