We talk a lot about code reviews, architectural patterns, and performance optimizations. But we often forget the most critical part of software engineering: the human on the other side of the pull request.

Great feedback isn’t about finding flaws. It is about building stronger code and stronger people.

My approach to code reviews and technical mentoring is guided by a simple principle: Be kind, but be clear.

When Giving Feedback

When you leave a comment on a pull request, remember that text is completely devoid of tone. A comment that sounds perfectly neutral in your head can read as a harsh attack to a junior developer who is already feeling impostor syndrome.

Do not just say: “This is wrong. Use a Map here.”

Say: “I think a Map might be more efficient here for lookups. What do you think?”

Ask questions instead of giving orders. Focus on the code, not the coder. And most importantly, when someone writes a genuinely elegant piece of logic, call it out! Praise is a powerful tool for reinforcing good patterns.

When Receiving Feedback

See feedback not as criticism, but as a gift. It is a free lesson on how to improve.

Do not get defensive when a senior engineer points out a flaw in your design. They are taking the time out of their own sprint to help you grow.

A culture where feedback is given with care and received with grace is a culture where everyone grows. As seniors, it is our job to champion that. We set the tone.