Why did we embrace code reviews?

While vetting offshore development teams, one of the teams’ leaders insinuated that Code Reviews is a sign of little or no faith in the teams’ technical skills. Then he proceeded to give us more reasons to abandon this process with his company by describing the process as a poor time management strategy. Since we had about 30 minutes left in our scheduled meeting, I thought it was appropriate to share with him and his team the benefits of code reviews. There are two reasons to embrace code reviews:

    1. Minimize bugs in shipped features

We understand that software development is very intensive intellectual work, developers have earned the right to make mistakes to learn from them. Using code reviews allowed us to:

      • Ensure that code match the requirements
      • Code respect our enterprise coding standards
      • Fewer defects --> less maintenance and bug tracking --> more time to deliver more features --> happier client
    1. We found the process to be a very cheap educational tool (business domain and technology)

Our developers are trained professionals, using the process to flex intellectual muscles, and programming superiority will not be tolerated in our organisation. When our leads discover code vulnerability, they cease the opportunity to mentor the developers. The process is used to share both business domain and technical knowledge; our team members are familiar with each other’s strength and weaknesses. Peer mentoring is paramount in our organisation, we build on each other’s strengths and eliminate weaknesses. Another critical reason to use code reviews is to give praise and credit when and where credit is due.

Add comment