📜 Apply these strategies when reviewing code (Part 2)

5 strategies to reduce friction when you review code.

Do you think you are dedicating your time to someone else when you are reviewing code?

You are not alone. I thought the same. But it’s your time. You are diving deep into the codebase. You are referencing software principles to improve concrete parts of the implementation.

It’s said that the teacher learns more than the students. I encourage you to think of Code Reviews (CRs) as time spent structuring your thoughts. This will reduce the resistance you feel against CRs.

We already went through a first round of CR mistakes and tips in 🚫 Avoid these mistakes reviewing code (Part 1). Today, we have 5 tips to make your reviews more efficient and reduce friction.

📑 #1 Write comments like a white paper: With references

The discussion goes nowhere when it’s about opinions. However, when I reference a single source of truth, it’s no longer about what you or I think.

When talking about styles, reference a style guide for the language. Usually, each company has some practices they follow. Keeping co…