Crafting Better Code Reviews

Vaidehi Joshi
May 2, 2017 · 13 min read
© geek & poke, http://geek-and-poke.com

Why even bother with review?

The original intent behind code reviews was that they would help us take collective ownership in the creation of our software. In other words, we’d each be stakeholders in our development process by having a hand in controlling the quality of our products.

1. Inspections

2. Walkthroughs

3. Short code reviews

What do developers think of code reviews?

The quantitative data

The qualitative data

Ultimately, what seemed to make or break a code review experience depended upon two things: how much energy was spent during the review process, and how much substance the review itself had.

Energy

Substance

How do we do better?

Instead, it is the act of introspection, reflection, and reevaluation of our collective code review culture that will allow us to build upon any kind of formalized review process we might have.

Easy ways to improve your code review process

The harder things — but the most important

I love code reviews in theory. In practice, they are only as good as the group that’s responsible for conducting them in the right manner.


Resources

Acknowledgements

Vaidehi Joshi

Written by

Writing words, writing code. Sometimes doing both at once.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade