Top 10 Obstacles to Faster Code Reviews and Better Code Quality

This is a short and sweet story about important facts to know and share about code quality and code reviews. You can also read more about this in our ebook.

680 companies were asked about their code quality and code review practices. Below are 10 of the most compelling learnings.

Disclosure: Codacy, the automated code reviews platform, has previously sponsored Hacker Noon. For Hacker Noon readers, they’re offering 15% off using this code: HACKERNOON.

The facts

1 We spent a significant amount of time reviewing code. In fact we spend on average 5 hours per week reviewing code or 12.5**% of our week looking at code**.

2As a developer, spending more than a day a week reviewing code doesn’t correlate with improvements in perceived code quality OR in more time shipping new features (as opposed with fixing bugs or paying back tech debt).

Diminished returns: spending more than a day per week reviewing code does not correlated with better perceived code quality

3 45% of developers say that ‘Lack of Time’ is the real obstacle to reviewing code while 34% say ‘Pressure to Ship’.

4 72% of developers say that their code reviews are blocking (don’t ship a line of code without being reviewed).

5 66% of developers require 1 person to approve their pull requests. 25% require 2 people. Less than 5% require more than 2.

6 53% of people monitor code coverage but 65% don’t have a minimum threshold of code coverage to approve a pull request.

7 29% of developers say the biggest problem in their project is “Workload” while VPs of Eng and Directors say “Delivery speed”. The third biggest problem for developers is “Management”

Who gets to review code? Two thirds of companies prefer the all hands on deck approach to code review.

8Regarding who gets to review code, having everyone in the team do it is the most common practice. Other alternatives are having owners of projects or modules or having senior developers review most of the code.

9Stricter code reviews lead to less time fixing bugs and more time delivering new features. Less strict code reviewers spend 31% of their time fixing bugs whereas stricter reviewers spend 24%. Regarding time focusing on new features: 43% and 54% corresponding.

10Developers spend 45% of their time fixing bugs or addressing technical debt vs of building new features.

Time spent on average per activity during development

You can also read more about this and other great learnings in our new ebook about code reviews:

Click to get the ebook