Beyond Code: The Key to Becoming a Better Developer

The Importance of Reading PRs

Today I wanted to talk about something that might be a little underrated. You might be thinking, what could that be?

So, the ability to read a PR. It's something I didn’t realize was much more important than I expected.

Understanding the Thought Process Behind PRs

The ability to read a PR and understand where the changes are happening, why someone made this change, and their thought process while making it is an amazing skill. It’s much more useful than I initially realized when I was starting out.

It’s definitely a difficult skill to develop—just looking at code and trying to piece together why and how someone did something without having to pull down the branch or run the code. Simply analyzing it from a PR perspective is challenging.

The Value of Strong Code-Reading Skills

But I think it really helps. It’s a fundamental skill. Once you get good at it, you naturally become better at reading code. You start recognizing when something looks off.

In fact, if you’re struggling to read the code, it’s often because it was written poorly. That in itself is useful feedback—if someone reviews your PR and finds it hard to follow, that’s a sign something needs improvement.

At the core of it, this skill is about reading other people's code. Reading your own code is usually easier because it follows your thought process. But being able to understand how others think when they code? That’s what really makes you a better developer.

Overcoming the Intimidation of PRs

I remember when I first started professionally. I’d open a PR, and immediately, I’d feel overwhelmed—so many changes, red and green lines everywhere.

I had no clue what was touched or changed. I didn’t understand the code at all.

At some point, I decided to push through that fear. I told myself, I can do this. I started poking at the PR, slowly piecing things together. And if I got really stuck, I’d pull down the branch and run the code to see what changed.

The Breakthrough Moment

Taking that first step—just looking at the PR and attempting to understand it—was the game changer. I realized it’s okay if it’s difficult. The key was to not give up.

Once you improve at reading PRs, everything starts clicking. You begin to follow the flow of thought behind the code naturally.

And beyond that, it helps unlock a deeper understanding of coding principles—like OOP, design patterns, and different frameworks.

The Significance in a Developer’s Career

This is a fundamental skill that every developer needs. If you’re working in the field, you’re not the only one pushing code—you’re going to be reading a lot of other people’s code.

Having this skill will make your work smoother and earn you respect. People will notice when you catch mistakes they didn’t see or suggest a better way to write something.

How to Get Started

My best advice? Give it a try. If you’re working, open a PR and attempt to understand what changes were made. If you’re unsure about approving, that’s fine—just go through it piece by piece.

If you’re not working at a company with PRs, try reviewing code with friends on a project. You don’t have to be perfect. Your PR comments can even be simple questions, like “Hey, what does this do?” That’s completely okay.