Code review is constant in engineering, and the tone of feedback shapes team culture. Giving and taking it kindly builds a stronger team. Here's how.
Comment on the code, not the coder
'This could break on null input — maybe guard against it?' works; 'why did you write it this way?' stings. Keep feedback about the code and constructive. It's a review of work, not a judgment of the person.
Be specific and suggest
Vague criticism frustrates; specific, actionable suggestions help. Point to the line, explain the concern, and offer a direction. And note the good parts too — positive feedback matters in reviews.
Receive it without ego
Frequently asked questions
How do I give kind code-review feedback?
Comment on the code not the coder, be specific and suggest solutions, and note the good parts too.
How do I receive code review well?
Without ego — reviews improve the code, not attack you; engage with the substance.
Why does review tone matter?
It shapes team culture; kind, specific review builds a stronger team.
How can I improve team communication?
Kerr University offers 1-on-1 coaching tailored to your industry — flexible, affordable, with 24/7 access and free certificate courses. Book a free 30-minute class.
Start with a free 30-minute class
See the Fast-Track Fluency Method™ in action and meet Digby in person. No risk, no obligation.
Book My Free Class