How Important Are Code Reviews In The Software Development World ?
The cost of resolving a software bug is extremely high if it is found later in the software development life cycle (SDLC). The Systems Sciences Institute at IBM reported that it cost 6x more to fix a bug found in production than to fix one identified during development.
Therefore when teams use code reviewing it helps them by filtering the leakage of bugs to production. The process of reviewing code allows to spot potential issues early that may arise from a piece of code, as well as giving the original developer the opportunity to refine their work and fix any problems that may have been introduced.
This is particularly important in agile projects, where the ownership of the product is shared and changes are made quickly and frequently. Frequent peer review in agile projects helps to ensure that changes are made in a way that does not adversely affect existing functionality or implementation and also provides a degree of quality assurance. Having more than one set of eyes examining the code adds an extra layer of security, helping to ensure the highest quality software is produced.
Code reviews also help to communicate and establish project ownership, encouraging team members to take ownership of the product that they are building.
It is also an excellent opportunity for the reviewing party to identify any areas where improvements can be made, allowing the original developer to incorporate these changes into their own code and subsequently providing a better product.
In addition, frequent and regular reviews can help to improve communication within a team, as well as collaboration and cooperation between team members.
Finally, and most importantly, code reviews are an invaluable process for training new developers, helping them to learn from the mistakes of others, as well as providing them with the opportunity to examine the work of others and find details that they may not have spotted themselves. In short, code reviews are an important part of the software engineering process for a number of reasons.
When Should Code Reviews Take Place?
Code reviews should take place as and where possible throughout the development process, ensuring that all errors and omissions are identified and corrected prior to release. It is often said that you cannot code well unless you code frequently, meaning that new errors will inevitably be introduced as the product is changed and evolved over time. Therefore, it is essential that these errors are caught and corrected during the development process, rather than waiting for release and potentially causing large scale disruption or even damage to the system. Code reviews should be a part of the daily practice of all developers, ensuring that all potential errors are caught and corrected before release.
Who Should Code Review?
Who should do code reviews? Ideally, you would want a mix of experience levels within a team, with some expertise in coding and some in business or project management. The mix allows for both new perspectives and a more in-depth understanding of the project, while the expertise levels bring in more valuable information and potential to improve existing processes and structures. Ideally, you would want some combination of the following roles:
- Software developer
- Product manager
- Analyst
- Tester
- QA person
- Architect
- DBA
“The more people that look at it, the more chance there is of someone finding something,” said Hemal Deepak, director of product management at Red Ventures.
Conclusion
Code reviews should not be considered a negative or positive experience and are merely a part of the process that allows us as a community to keep improving and evolving software.
