Agile and DevOps practices enable faster delivery, higher quality and lower risk. Adoption of automated Code Review and Continuous Inspection practices help deliver on this promise.
"The average defect detection rate is only 25% for unit testing, 35% for function testing, and 45% for integration testing. In contrast, the average effectiveness of design and code inspections are 55% and 60%", in Code Complete by Steve McConnell
Code review is systematic examination (often referred to as peer review) of source code. Of course, modern applications now include services, libraries, images etc.
Continuous Inspection is very frequent inspection of software to provide early warning of maintainability and other code quality issues, such as coding standard issues, static analysis findings, web vulnerabilities, security and licensing risks.
A successful strategy for code review and inspection requires balance between automated processes and a non-threatening, collaborative environment in order to avoid regimented peer reviews that stifle productivity and hinder adoption.
Modern Dimensions CM implementations enable enterprise teams to make code review and continuous inspection a habit that will speed delivery, increase quality and reduce risks in your development and deployment pipeline.
- Highlighting just the lines of code that have changed increases the efficiency and effectiveness of reviewing each commit, increasing the ability to find and collaboratively discuss coding defects.
- A code review that presents both the highlighted code changes AND any continuous inspection findings optimizes your inspection rate and time on every commit.
- Providing the ability to collaborate with the developer in reviewing while not forcing a pace that is uncomfortable to developers or reviewers encourages engagement and focus while allowing any necessary breaks for a task over a period of time can greatly improve quality of work.
- Incorporating a code review checklist enables teams to decide how you will measure the effectiveness of peer review and name a number of tangible goals. Checklists can be the most effective way to eliminate frequently missed steps and avoid the challenges of standardizing and avoiding omissions.
- Conducting the peer review on each commit, together with any code annotations, guides the reviewer through the changes in sequence, proving insight into the reasons behind code modification and insights into any inspection findings.
- Embracing the "shift left" feedback and results from continuous inspection optimizes your code review process beyond your wildest dreams, establishing an automated process for fixing defects and resolving inspection findings.
I urge all Dimensions CM customers to upgrade to our latest release 14.3.3 and adopt and leverage peer review and continuous inspection to create a positive review culture and make code review a habit.
As development teams and groups, we should all be creating an environment in which friends don't let friends commit "unreviewed" code to the mainline.