20 questions for valuable code reviews
Tags: engineering, webdev
Published: 2022-01-01 05:57:04

---
title: 20 questions for valuable code reviews
published: true
date: 01/01/2022
tags: #engineering #webdev
canonical_url: https://darraghoriordan.com/2021/11/28/21-questiosn-how-to-do-valuable-code-reviews/
---

I recently had an interesting discussion around the value of doing code reviews and the value of mandatory code reviews.

I think code reviews are extremely valuable and should be done by most organisations and teams.

A _valuable_ code review will 

- pass institutional knowledge around the org
- help all engineers grow their skills
- maintain quality in the face of all the other time pressures your team faces

But how do you keep a code review valuable? 

<!-- end excerpt -->

1. Automate instead of PR checklists
2. Focus on code readability and functional correctness

## Automate instead of PR checklists
Anything that can be automated must be automated. Engineers are expensive! Don’t waste your time on code formatting or spell checking if at all possible.

It's OK to have some checklists in a PR template but you should be always be actively working to remove checklist items through automation or engineering culture.

## 20 code readability and functional correctness code review questions

1. Is the intent clear?
1. Is there needless duplication?
1. Could existing code have solved this?
1. Is this an atomic commit?
1. Could this be simpler?
1. Are there obvious logic issues?
1. Does it need tests?
1. Are the tests comprehensive and clear?
1. Are there any security issues or considerations?
1. Are there any accessibility considerations?
1. Are there any PII considerations?
1. Is it instrumented? Are there relevant analytics? Are there relevant production logs?
1. Are there revert scripts for database changes?
1. Is the database work ACID? Is it transactioned sensibly?
1. Does this feature need to be turned off in the future?
1. Is it easy to turn it off?
1. How easy is it to delete the feature code as a whole entity?
1. Does the code respect Command-Query separation?
1. If DDD - Are there well defined aggregate roots, value objects, enumerations?
1. Will there be any issues recovering from a transient failure? Is the solution distributed in an unexpected way?

## A note on “nits”

In general I do not look for coding style, syntax I don't like, styling or spelling errors in a code review.

If these things are important to your team then just use your CI system to detect and fix issues automatically.

In typescript/javascript we have ESlint, Prettier and Vale to detect and fix issues automatically. There will be similar tooling for your language and framework of choice.

Consistency IS important. If an entire code base is using some syntax but you prefer a different syntax that is functionally the same, you should use the existing syntax unless the entire team agrees with you and there is a plan to change the code everywhere.

## A note on mandatory code reviews

The PR system developed by GitHub was for Open Source contributions by distributed teams. Mandatory PRs might not be relevant for a team with consistent levels of engineering capability and knowledge of the system.

I do feel that if code reviews are mandatory it means they won’t be bypassed when the pressure is on.

When the team under pressure is when you really need code reviews the most. If some software is forcing one positive code review then a single developer can’t be pressured into putting dodgy code out to customers.

## Summary

Code reviews that focus on finding nits, syntax you don't like, spelling errors and things like that are not a valuable use of your time. Automate these with tooling instead.

Code reviews that focus on code readability and functional correctness are extremely valuable to the entire organisation, long after you have moved on to another project.

If don't enjoy code reviews, try changing their purpose and start evangelising what a good code review looks like.