Review Etiquette and Collaboration
What you'll learn: How to build a positive, productive code review culture by focusing on empathy, clear communication, and critiquing code rather than people.
The Human Side of Reviews
Code reviews aren't just technical exchanges—they're human conversations. When done well, they strengthen teams and improve code quality. When done poorly, they create tension, slow progress, and damage trust. The difference lies in how you communicate.
Focus on the Code, Not the Person
Always remember: you're reviewing code, not judging the coder. Say "This function could be simplified" instead of "You made this too complicated." The distinction seems small but matters enormously. One feels like helpful collaboration; the other feels like personal criticism.
Think of it like restaurant critics reviewing a dish, not attacking the chef's character. You want everyone to improve together, not defend themselves.
Key Principles
Be empathetic. Remember when you were learning—or when you've made similar mistakes. Everyone has different context, time pressures, and knowledge gaps.
Communicate clearly. Ambiguous comments like "This seems weird" leave the author guessing. Instead, explain why something concerns you: "This approach might cause issues with concurrent access—have we considered using a lock here?"
Assume good intent. Your colleague isn't trying to write bad code. If something seems off, ask questions before making declarations: "Help me understand why we chose this pattern?"
Be responsive and timely. Whether you're reviewing or responding to feedback, delays hurt team momentum. Respect everyone's time.
Celebrate good work. Reviews aren't just for finding problems. Acknowledge clever solutions and clean code. "Nice catch on that edge case!" builds morale.
Key Takeaway: Positive review culture comes from treating reviews as collaborative learning opportunities, focusing feedback on code quality rather than personal criticism, and communicating with empathy and clarity.