Welcome to the final part of BSP Software’s ‘Code Review’ series
Part 1) Author and Reviewer Preparation
Part 2) Readibility
Part 3) Structure
Part 4) Algorithmic soundness
Part 5) Bugs found, now what?
Part 6) Implementation strategy
Peter Gabris, MD of BSP Software Inc
In this section we focus on
Part 7) Tools of the trade
Code review can be done without any tools. However, a lot of time and effort can be saved by the right tool. The most popular, affordable and recommended general tool is CodeCollaborator by SmartBear Software.
Efficient version control system is necessary as well. The current market leader is Subversion in combination with TortoiseSVN. Both are free.
Code profilers and review tools depend on the programming language and development environment. Many can be customized according to the company coding policy.
Implementation steps
Project Managers
- Familiarize yourself with the Code Review Process document
- Read this document
- Ask team leader of each project to name the code reviewer for each program (or program type) in the project
- Accept the programming step 100% done only after you received the code review confirmation.
Team Leaders
- Familiarize yourself with the Code Review Process document
- Read this document
- Ask team leader of each project to name the code reviewer for each program (or program type) in the project
Programmers
- Familiarize yourself with the Code Review Process document
- Make sure each programmer in your team had selected the code reviewer and the code reviewer accepted. If a single piece of code is developed by more than one programmer, only one code reviewer is needed.
- Get ready to resolve disagreements between programmers and reviewers with a great diplomacy.
Management
- Remember that your programmers are doing very demanding work. The requirements, tools, environment and methods evolve permanently and permanent learning is an integral part of their daily job.
Feel free to leave any questions or comments below