Code Reviews : Both Technical and Personal

Code reviews feel technical, but they’re deeply personal. You’re not just reviewing code; you’re reviewing someone’s thinking, effort, and judgment. When that human side gets ignored, reviews turn cold fast.

A few core issues tend to show up:

1. Code is treated as objective, people aren’t
Reviewers often act like they’re critiquing math, not work made by a person under constraints. Comments like “This is wrong” or “Why would you do this?” may be logically accurate, but emotionally blunt. Precision without empathy lands as dismissal.

2. Asymmetry of power isn’t acknowledged
Senior engineers reviewing junior engineers, staff reviewing contractors, leads reviewing teammates—it’s rarely peer-to-peer. When reviewers forget that imbalance, even neutral comments can feel like judgment or gatekeeping.

3. Efficiency is valued over kindness
“Just be direct” becomes an excuse to skip tone, context, or curiosity. The problem is that efficient feedback that shuts someone down is actually inefficient long-term: people disengage, stop asking questions, or play it safe.

4. Intent is assumed instead of asked about
Instead of “What was the reasoning here?”, reviewers jump straight to “This should be X.” That erases context the author might have—deadlines, legacy constraints, partial refactors—and sends the message that their judgment didn’t matter.

5. Written text amplifies bluntness
Code review comments lack facial expression, timing, and warmth. What would sound fine in a conversation can read icy or hostile on a screen, especially when stacked comment after comment.

---

What sensitivity actually looks like (without being “soft”)

This isn’t about coddling or avoiding critique. It’s about respectful clarity:

• Replacing judgment with curiosity

  “What tradeoffs were you considering here?”

• Separating preference from requirement

  “Nit / style preference:” vs “This will break in case X.”

• Acknowledging effort

  “Thanks for tackling this—one thing I’m unsure about…”

• Explaining why, not just what

  “This change helps because it avoids race conditions.”

Good reviewers don’t just improve code—they make people better at writing it.

---

The uncomfortable truth

A lot of “unsensitive” code review culture is inherited. People repeat the tone they endured, assuming that’s what professionalism looks like. But technical rigor and human decency aren’t opposites—they reinforce each other.

Teams with psychologically safe reviews:

• Catch more bugs

• Share more context

• Learn faster

• Burn out less

If you’re feeling this issue personally, you’re not being thin-skinned—you’re noticing a real gap in how engineering culture treats people.