11 Best Practices for Peer Code Review

11 Best Practices for Peer Code Review


How many lines of code (LOC) do you review at a single time? According to a study by Cisco, reviewing more than 400 LOC over a 60-90 minute spread significantly diminishes your yield, while staying in these parameters has a 70-90% yield.

Peer code review is common sense - it identifies bugs, encourages collaboration, and keeps code maintainable. However, some of the techniques for code review have become inefficient or downright ineffective. New approaches to code review can help optimize the review process, improve the overall quality of code, and makes the most of the entire team’s time.

Check out these 11 best practices to help maximize your coding process and reduce potential problems. Read this paper and learn these practices, including:

  • Why you should establish quantifiable goals and use checklists
  • Fostering a good code review culture
  • The ego effect: the benefits of doing some code review even if you don't have time
  • And more.
SmartBear Software
28 Aug 2012
28 Aug 2012
10 Page(s)
White Paper
Already a Bitpipe member? Login here

Download this White Paper!

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.