Should you call out code style issues in a code review?

By Dan Bader — Get free updates of new posts here.

One of my friends works at a software company where all code changes must be reviewed before they’re deployed to production – I think that’s great. However, he finds that his team spends too much time discussing code style and formatting issues in their code reviews.

He feels that code style and formatting discussions slow down development because they often require a lot of back and forth between reviewer and reviewee.

And sometimes these conversations take a turn for the worse and erupt into heated arguments.

I wanted to take a few minutes to share my thoughts on this topic.

Is pointing out mechanical issues like code formatting in a code review a good idea? Is it worth your time?

Giving feedback on things like code formatting or adherence to a style guide can turn into a never-ending story and cost a development team a lot of time.

In the worst case this kind of feedback can soak up huge amounts of engineering resources:

For example, if review comments need to address style issues, functional problems with the code (== actual bugs!) might not be identified and get waved through.
It costs valuable developer time to argue over code styling and formatting. This might also lead to conflicts within the team by turning into a holy war around minutiae like “tabs vs spaces”.

However, code formatting issues should almost never come up during a code review.

Mechanical style issues, like tabs vs spaces, or basic naming rules for variables, shouldn’t even make it to the code review stage.

Automated tools, like linters and code formatters, should identify these issues before the code is opened up for peer review. Run these tools on a build server so that devs don’t need to trigger them manually.

Remember that the best code reviews should provoke discussions — and spending time on basic formatting issues won’t help with that goal.

<strong><em>Improve Your Python</em></strong> with a fresh 🐍 <strong>Python Trick</strong> 💌 every couple of days

Improve Your Python with a fresh 🐍 Python Trick 💌 every couple of days

🔒 No spam ever. Unsubscribe any time.

This article was filed under: code-review, craftsmanship, and programming.

Related Articles:

7 ways to avoid aggravation in code reviews – Thankfully many software companies have adopted code reviews as a best practice these days. An overlooked aspect of how code reviews are conducted is how they can also affect the relationship between engineers negatively.
Watch me do a “live” Python code review for a reader – This is a bit of an experiment – but you might find it interesting!
Python Code Review: Unplugged – Episode 2 – This is the second episode of my video code review series where I record myself giving feedback and refactoring a reader’s Python code.
Python Code Review: Unplugged – Episode 3 – In this third episode of my video code review series I take a look at a reader’s web scraping project and start adding some unit tests to it.
Should you worry about code reviewing someone more experienced than you? – Doing your first code review for something written by a senior member of your team is scary. As a novice programmer it’s easy to think that only beginning or intermediate developers struggle with this.

Latest Articles:

Interfacing Python and C: The CFFI Module – How to use Python’s built-in CFFI module for interfacing Python with native libraries as an alternative to the “ctypes” approach.
Write More Pythonic Code by Applying the Things You Already Know – There’s a mistake I frequently make when I learn new things about Python… Here’s how you can avoid this pitfall and learn something about Python’s “enumerate()” function at the same time.
Working With File I/O in Python – Learn the basics of working with files in Python. How to read from files, how to write data to them, what file seeks are, and why files should be closed.
How to Reverse a String in Python – An overview of the three main ways to reverse a Python string: “slicing”, reverse iteration, and the classic in-place reversal algorithm. Also includes performance benchmarks.
Mastering Click: Writing Advanced Python Command-Line Apps – How to improve your existing Click Python CLIs with advanced features like sub-commands, user input, parameter types, contexts, and more.
Working with Random Numbers in Python – An overview for working with randomness in Python, using only functionality built into the standard library and CPython itself.

← Browse All Articles