Code review should be systematic. It should also be efficient. While those two statements may seem extremely simple, it can be difficult to maintain a high level of efficiency without accurate statistics and benchmarks keeping you on the right track. Of course, the main benefit of code review is that finding errors in the code during the initial development phase is much less expensive than, for instance, receiving a support ticket after you've released the product. So why not make sure you're finding as many errors as possible as quickly as you possibly can? I recently dug deep into our archives and pulled out this video featuring peer code review guru, Jason Cohen. Back in 2011, Jason presented findings from a practical study he had been a part of earlier that year with Cisco Systems, a customer of CodeCollaborator. For your convenience, I've shortened the video to include two of the most meaningful tips:
- After roughly 65 minutes code review becomes less efficient.
- When reviewing more than 300 lines per hour code review becomes less efficient.
The video above provides more details about the statistics behind Jason's assertions and how you can make your own code review process as efficient and painless as possible. For even more information, click below to download the eBook or order a free copy of Jason's book, "Best Kept Secrets of Peer Code Review." See also: