Stage 6 · Lesson 4 of 6

Harsh code review comments

Code review is where many engineers first meet blunt written feedback. A comment like "this is wrong" or "why would you do this?" can sting, especially in your first months. Remember that reviewers often write fast and in short form, and that the review is about the change, not about you.

Reply to the content: ask for the reason if it is not clear, agree and fix, or explain your choice briefly with evidence. If a reviewer is consistently rude, raise it calmly with your lead. Later, when you review others, write the kind of comments you wish you had received.

Common traptaking every short comment as contempt, or arguing every point to prove you were right.

A question to check yourself and an AI practice session come when you add the roadmap to your account. Add it

Resources for this stage

Start with

BookPaid
Difficult Conversations: How to Discuss What Matters Most
Douglas Stone, Bruce Patton, Sheila Heen (Penguin Books) · Paid book
From two of the authors of the feedback triggers idea, on hard conversations of every kind

Practise

The Update, the Vent, and the Disaster
How to bring a problem to your manager, and what they are listening for

Keep handy

One on One Meeting Questions
Specific questions to ask for useful feedback in one-to-ones

Also worth your time

The Confidence Gap (Russ Harris)ReadPaid
On acting on what matters while the fear and self-doubt are still there

Struggling right now? If you are in danger or thinking about harming yourself, contact local emergency services or a crisis line: Find a helpline (any country), Umang (Pakistan), Tele-MANAS, 14416 (India).