3 Simple Rules to give effective Code Review feedback

Every developer on a team that cares about quality will eventually participate in the Code Review (or Pull-Request / PR) process.

As a developer regularly sought after to provide PR input, I know being an effective reviewer can appear as an art form. In reality, thoughtful application of a simple set of rules is all it takes to succeed.

Before jumping into the how, let's discuss the why.

Why should you care about being an effective Code Review-er?

The PR process is about more than catching bugs before production. It gives an opportunity to spread knowledge across the team, raise the standard, and guide the codebase's future direction.

For the participants, it is a prime chance to learn from each other, and impart your technical influence. Both sides are vital to your growth as a dev.

Now that you care, how can you do it well?

Above all else, remember there is a human on the other side of that code. We've all been guilty of getting attached to our code, be respectful and enjoy the collaboration.

This #ship30for30 #atomicEssay was shipped with this twitter thread:


Thanks for reading. If you enjoyed the article subscribe via RSS feed or enter your email in the box below 👇