Why Contributors Should Review Code (and How to Start) !!!!!

Community
1

Let me start with a story…

Recently, I was tagged to do a code review for the first time in an open-source project. My first reaction? Hesitation. I thought, “Wait… I’m just a contributor. Isn’t code review only for maintainers?”

Later, while talking to a friend, she joked:

“Yeah, if I were a maintainer, I’d be scrambling my head too, because I hate reading other people’s code.”

She laughed. I didn’t. Because deep down, I related. A scary thought came to me: What if, someday, I become the lead of a project but I hate reading other people’s code? Would I still be a good lead?

That thought stayed with me.

How I used to approach open source

My workflow was simple:

  • Use a project I like.
  • Spot an inconsistency or bug.
  • File an issue.
  • Work on a fix.
  • Open a pull request (PR).
  • Leave it for the maintainers to review and merge.

I genuinely believed reviewing code was “their job.” After all, maintainers are the ones with merge rights.

But then something clicked:

As contributors, we may not have the authority to merge—but we absolutely have the ability to add value through reviews.

Why contributors should do code reviews

I realized code reviews aren’t just a “maintainer’s task.” They’re an incredible way for contributors to grow and engage:

  1. Learn new areas of the project – Every PR touches a corner of the codebase. Reviewing it expands your awareness.
  2. Understand problem-solving approaches – You get to see how someone else interpreted and solved an issue.
  3. Sharpen your critical thinking – Reviewing demands careful reading, observation, and reasoning.
  4. Connect with people – A thoughtful review opens conversations with both contributors and maintainers.

How to start contributing through reviews

If you love a project, code review can be a great entry point. Here’s how you can begin:

  • Read the issue linked to the PR. Understand the problem first.
  • Read the PR description. See what the author is aiming to fix or add.
  • Run the code locally (if possible). Does it work as expected?
  • Give constructive feedback. You don’t need to be an expert—asking questions is valuable too.
  • Be respectful and encouraging. Someone has put time and effort into that code.

Final thought

Code review isn’t just about gatekeeping quality. It’s about learning, collaborating, and growing together. So, next time you’re contributing to an open-source project, don’t wait to be a maintainer—jump into code reviews. It might just be the best way to level up.

A small personal update :seedling:

I’ve got stuff to focus on until November 15, so I may not be as active here for a little while. I’ll still try to show up whenever I can, because I truly enjoy contributing to open source and connecting with this community.

Thanks for understanding, and I’m looking forward to being more active again after my exams. In the meantime—happy coding and collaboration to all of you! :sparkles:

1 Like