One code review comment can wreck your whole afternoon, even when the comment is about a variable name. I will show you why that happens and the small daily rep that takes the sting out of it.
Quick background so you know where this comes from. I'm Christopher. I spent nine years in the Marine Corps, then moved into software and data engineering, including edge computer vision work for the Air Force on a project called Athena. In the Marines, feedback came loud, blunt, and in front of everyone. You learned fast that a correction was about the task, not about your worth. And I still caught myself in tech reading "nit: this could be simpler" and spending twenty minutes wondering if my lead thought I was bad at my job.
If that is you, you are not thin skinned. Your filter is reading the wrong message.
What you actually hear
Your reviewer writes: "Can we pull this into a helper?"
What you hear: "You don't know what you're doing, and now everyone on the PR can see it."
That gap is the whole problem. The comment is about twelve lines of code. The story you tell yourself is about you. So you either get defensive and argue every point, or you go quiet, accept every change without thinking, and open your next PR with your stomach in a knot.
Why it hits so hard
I don't believe you build confidence. I believe you unhide it. The same developer who calmly walks a junior through their first rebase can feel crushed by a two word comment on their own code. The skill is still there. What changed is how exposed the moment feels.
Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe a teacher marked your work in red in front of the class. Maybe an early reviewer was genuinely harsh. Maybe you just grew up where mistakes meant trouble. Your filter took notes: being corrected equals being exposed, and being exposed equals danger.
So now, when a review comes in, the filter skips past the five approvals and the "nice catch" and locks onto the one comment that sounds like criticism. You cannot logic your way out of that. Telling yourself "it's just code" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.
The daily rep: compliment a stranger
Once a day, give one genuine, specific compliment to a stranger. Great shoes. Love that coffee mug. Your dog looks thrilled to be here. Say it, smile, keep walking.
I know that sounds unrelated to a pull request. It is the same muscle at low stakes. You are putting yourself out there with zero control over how it lands, while your body braces for a bad reaction. The first few will spike your heart rate. Then they stop.
The rule that makes it work: the win is the action, never the result. They ignore you, win. They say thanks, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says putting yourself out there only counts when people approve. The rep is the point.
That is rung one of a short ladder:
- Genuine compliments to strangers
- Compliment plus a quick "how's your day going?"
- A longer conversation, no agenda
Move up only when the current rung stops spiking you.
Bring it to your PRs
Once the stranger reps feel easy, run the same reps on your reviews.
Read it twice, answer it once. First read is for your feelings. Let them happen. Second read is for the code. Only reply after the second read.
Rewrite the comment in plain words. "Can we pull this into a helper?" becomes "This logic repeats, a helper would make it easier to test." Strip out the tone you imagined and keep the request. Most of the sting lives in the tone you added.
Ask one question per review. "Do you mean a shared helper or one local to this file?" A question turns a judgment into a conversation, and it shows you are engaged instead of hiding.
Push back once, politely, when you disagree. "I kept it inline because it's only used here. Happy to change it if you feel strongly." That one sentence is a huge rep. Each time it goes fine, your filter learns that disagreeing is safe.
Say thanks in the thread. "Good call, that's cleaner." Closing the loop in public trains your brain that feedback ends well.
What Athena taught me about feedback
On Athena, edge sensors ran a local model. When it flagged something significant, it sent context from before, during, and after the event back to AWS so the models could be retrained. Nobody treated that data as an insult to the model. It was the only way the model got better.
Code review is the same loop. A comment on your PR is not a verdict on you. It is training data for you and for the codebase. The developers who grow fastest are not the ones who get the fewest comments. They are the ones who can take a comment, use it, and ship the next PR without flinching.
You already know how to take feedback. Old training just taught you to hear it as an attack.
Your mission this week
- Compliment one stranger a day for seven days.
- On every review you get, read it twice before you reply.
- Ask at least one clarifying question on a review.
- Push back politely on one comment you genuinely disagree with.
- Thank a reviewer in the thread every time a comment makes your code better.
Then tell me in the comments: what is the review comment that stuck with you the longest, and was it really about you or about the code?
