Posts Tagged ‘vital elements’

Peer code review or as it is often referred to as simply code review, is an in depth line by line walkthrough or review of a code module. Each segment of the code is inspected to highlight faults and look for areas of improvement which ensures business needs are met. Usually after peer code review has been performed there will be a meeting between team members to discuss the findings and suggestions on improvements in the code.

A lot of programmers would argue quite aggressively that reviews are far too time consuming, however it is well noted that the drawbacks almost always out weight the benefits received from well planned peer reviews. The benefits are many and they include, fewer bugs, less rework, more pride and all round better team communication.

Code review methodologies come in various shapes and sizes and each company that writes code for a living tend to have their own custom process, however there are some common elements to most review processes. The three step model is very common and includes preparation, review and follow ups. A well thought out review process will need to include all three of these vital elements.

Even the most efficient review process can come across challenges the most common ones will include time, preparation, initial frustration and the need to show commitment.

Peer reviews are known for the enormous amount of time they take up. Like any other meeting a strong focus on the topic, being familiar with the process and establishing solid rules and principles can help keep the time down to a reasonable level.

Dealing with team members who are not familiar with the code review process can be a highly frustrating element. A review team need to devise a structure that suits all and only deviate from it in exceptional circumstances. Do this and over time all members will come a custom to the process and the review will run smoothly.

Random peer reviews do offer some benefit but also raises a large question over commitment. You should really be looking to implement the reviews for every module, and sticking to a consistent program. Preparation is key to any successful code review process and sometimes the reading of unfamiliar documentation takes time and distracts from the coding process, however this is sometimes necessary and the benefits will be reaped at a later date.

Author: Tom Greaves
Article Source: EzineArticles.com
Provided by: Make PCB Assembly