We push more than 250 commits every day. More than 30 people work on 15 projects. How do we keep the quality high and in the same time make sure that the best practices are spreading within the team and mistakes are not being repeated?
As we started to think about this problem we thought about code review. Seems like everyone knows that code review is a valuable tool but a lot of teams struggle with implementing it because of the overhead they feel they just can’t afford right now.
Here is how we keep the overhead minimal and make sure no one skips this very important step:
Code review is usually seen as a way to keep the code quality high. We see it also as a way to encourage learning, spreading best practices and avoiding repeating the same mistakes. I our case the overhead is minimal (5-10% of the time is being spent reviewing other peoples code) and the gains are huge.
What’s your experience with code review?
And updated and more in-depth version of this article is available at A quick guide to peer code reviews