Monthly Archives: May 2013

Code Review: How do I prep for a peer code review? You should create a self-checklist with common mistakes that you have made in the past and use this to help remind you of things to look for in your … Continue reading →

Code Review: What do you review in a peer code review? All changes made should be reviewed in a code review; however, it is normal to focus in on key areas. It is okay for the author to give some … Continue reading →

Code Review: How long is a peer code review? The code review process has been researched and studied since 1976, and it has be established and re-established that the maximum product code inspection rate is 200 lines of code per … Continue reading →

Code Review: When do you do a peer code review? A peer code review can be done prior to check-in or after check-in. Quote: “I find most people come down strongly on one side or another; and since we make … Continue reading →

Code Review: Does the reviewee have to be present at a peer code review? A peer code review can be done shoulder to shoulder or pass around via e-mail/TFS. Over the shoulder reviews do require the reviewee to be present … Continue reading →

Code Review: Who should be involved in a peer code review? A peer code review involves another developer on the same team (peer), regardless of seniority. A junior developer can learn while reviewing a senior developer’s code and can still have good … Continue reading →

Code Review: What is a peer code review? A code review is the process of making source code available for other developers to review with the intention of catching defects and design errors which in turn results in improved product … Continue reading →