Stage 4 · Lesson 4 of 8
Receiving code review without taking it personally
is one of the fastest ways to learn in a first job. The comments are about the code, not about you, even when they are short or blunt. Read every comment and reply to each one: fix it, discuss it or ask about it.
If you do not understand a comment, ask what the reviewer means rather than guessing. If you disagree, explain your reason once, politely. If the reviewer still disagrees, accept the team's decision.
Note comments you get again and again, and fix that pattern in future changes. Many teams label comments as blocking (must be fixed before merging) or ; if yours does not, ask how to tell.
Common trapchanging everything silently without understanding it, or arguing over every .
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GuideFreeGoogle Engineering Practices
Google · Intermediate
Google's guides for change authors and reviewers: small changes, good descriptions and handling comments
- BookPaidThe Missing README: A Guide for the New Software Engineer
Chris Riccomini and Dmitriy Ryaboy (No Starch Press) · Beginner · $29.99 print, $23.99 ebook
The testing, code review, delivery and on-call chapters written for a new engineer