Matt Stauffer on YouTube · Open on YouTube
Professional practice · Competent · Lesson 35 of 98 · 15 min video, then about 5 hours of practice
Giving and receiving code review
After this you can review a pull request for correctness, clarity and risk, write comments that are specific and kind, and respond to feedback on your own code without defensiveness.
Why it matters
Code review is where most learning on a team happens, and juniors are expected to review as well as be reviewed. Look first for correctness and risk (does it do what it claims, what could break), then design and clarity, and only then style. Write comments about the code, not the person. Ask questions when you are unsure. When receiving review, assume good intent and treat every comment as free mentoring. Trap: rubber-stamping because the author is more senior. Questions from juniors catch real bugs.
How to use this resource
A senior developer's actual review process, step by step.
Go further
Go deeper