Growing talent via software reviews

 

The joys of being a new techie. That special time in your life when you have just learned MVC and now think you know everything. Good times.

Of course, everyone else in the team wishes they could slap the smugness out of you. Still, the energy is good and that is what will help the coder mature to a master engineer.

This will however not happen by itself. The senior team members must nurture the new talent.

One of the most potent ways of doing so is through a software review.

Unlike a retrospective, a software review is technical. Its focus is on the craft of software development rather than product improvement.

Some common outcomes of software reviews include:

  1. Robust design
  2. Code that is easier to maintain
  3. More literate code. See Name well or go home
  4. Fast growth of talent

So what exactly do you need to do to run a successful code review?

Before the review

  1. Invite all developers on the team to the meeting
  2. Ensure that everyone has access to the latest code
  3. Highlight the objectives of the review

During the review

  1. Gather everyone around one computer, or project code to a screen
  2. Reiterate that the only goal of the session is to improve the design of the code, not to attack anyone. The entire team is responsible for the product no matter who wrote which line of code
  3. The developer who wrote the code walks through the code explaining it along the way
  4. Trivial details can be skipped
  5. The other team members can comment on various aspects of the code such as naming scheme, reliability of external services and even choice of language if appropriate
  6. Discussions on alternative paths are encouraged. This is meant to be a lively meeting, all ideas are valid
  7. Improvement suggestions can then be agreed on by the entire team.
  8. This process can be repeated for all team members

After the review

  1. Team members should go ahead and implement the recommendations that were collaboratively arrived at
  2. Remember the goal should always remain to improve the code

Have you ever carried out a review before in your own organization? How did it go?

Talk to me on my twitter @jchex or in the comment section below.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Published by

jchencha

API Engineer