The Five Types of Code Reviewers


Team-Driven Developer

A newsletter with tips and tools for building software as a team

Many companies today have a formal code review process to prevent engineers from unilaterally merging their changes directly into production. This check exists for a handful of reasons: code maintainability, defect detection, and SOX compliance, to name a few.

If you're on a team with a mandated code review process, part of your job now includes navigating the code review process to get the approvals and feedback you need to ship quickly.

If you can’t get past the review, you won’t be able to get your code to production (where the impact is).

In this process, you’ll soon discover that not all code reviewers and team cultures around code reviews are created equal.

Today, I want to share the five common types of code reviewers and some strategies you can use to work with each to get your code merged.

Let's dive in!


Team-Building Exercise

Instead of focusing on the team and how it works together, the Team-Building exercise this week is all about you.

In particular, what kind of code reviewer are you?

Do you take too long to review code? Maybe you speed through them faster than you should.

Perhaps you leave too many or too few comments. Maybe you haven't figured out how to give feedback that lands.

And a great question to consider: do people enjoy having you review their code? Maybe be bold and ask a teammate their opinion.

Whatever the answers are, think a bit about how you could improve your code review skills and demeanor to help your team ship code more code faster and safer. Pick one goal for yourself in the upcoming iteration and see if you can make some progress.

Like most things in leadership, you have to go first to create change. Asking others to get to reviewers faster to help your code get merged faster when you put off a review for as long as possible isn't a great posture toward your team.

Go first and become the reviewer you'd want to have to review your code.


Here are some more resources from me to help you build better teams!​

  • 📕 Code Review Champion - My book on code reviews will help you become a world-class code reviewer. From giving kind feedback to navigating conflict, this book can help anyone wanting to sharpen their code review skills.
  • ❓​Questions for Devs - Building a team takes more than catching up about your weekend at standup. I've used these questions to build relationships with my team and push past the same old surface-level conversations.
  • ​📋 Pull Request Template - Maximize your efforts in pull requests by giving context right at the beginning of a new pull request. Copy and paste this template into your repo, and voilà!
  • 📊 ​Code Review Metrics - Start measuring how your team tracks against a few common code review metrics. This python script will pull your GitHub pull requests and generate a CSV you can slice-n-dice to get the data you want. It also has graphs! As this is an open-source project, your contributions and feedback would be great!

Other Creators I Recommend

Image for Building Custom SaaS Web Apps

Building Custom SaaS Web Apps

by Thomas McGee

I’m a web developer by trade, but I’m a creator at heart. As such, I constantly find myself making, designing, and coding new things to make life easier for creators of all kinds. Whether it be Radarist for managing your projects and tasks or Startboard for easily organizing your web bookmarks—I’m here to make it easier for anyone to earn online.

Image for Build It Better Newsletter

Build It Better Newsletter

by Jonas Fleur-Aime

Creating great software is not just about completing new features faster, submitting more pull requests, or fixing bugs. Every Wednesday I publish tips and tactics to help you meet tough deadlines, tackle tech debt, handle scope creep, manage stakeholders, make sure you're building what customers actually want, and more. I'll draw on what I've learned after spending 15 yrs as a software developer, Engineering Manager, CTO, and startup advisor.

113 Cherry St #92768, Seattle, WA 98104
Unsubscribe · Preferences

Dan Goslen | The Team-Driven Developer

Learn the tips and tools for building software as a team! Every other week, I send a long-form article, a team-building exercise, and resources to help you build better software teams so you can build better software.

Read more from Dan Goslen | The Team-Driven Developer

Team-Driven Developer A newsletter with tips and tools for building software as a team We've recently started a group at Webflow to enhance our existing code review process.And it made me think of an older article I wrote all about the point of pull requests. In a nutshell, pull requests aren't the same as a code review, but they are a common channel to help code reviews run smoothly. I rewrote and added some parts of the article based on the discussions we were having as a group, and wanted...

Team-Driven Developer A newsletter with tips and tools for building software as a team If you’ve ever joined a new team, tackled a legacy codebase, or stepped into an unfamiliar domain, the feeling can be overwhelming. There’s too much to know—and not enough time to learn it all. That’s why I use a model I call traversing the knowledge graph. It helps me orient quickly, pull in the most relevant context, and start contributing with confidence. In this post, I’ll describe: How I think and...

Team-Driven Developer A newsletter with tips and tools for building software as a team You’re staring at your editor. The code should work, but you’ve been fighting an error for a full day. You can’t figure out the problem no matter what you try. Or you’ve been staring at an empty file, wondering what code to write. You’ve got a vague Jira ticket, a lack of context, and a codebase that is difficult to understand. You’re blocked. Now, what do you do? It’s tempting—easy, even—to ping someone...