If you write code, you should review code. That’s it. That’s the talk.

There are quite a few “reasons” why developers at various levels find themselves code-review averse: impostor syndrome, time constraints, and area of expertise are a few I’ve heard. For code owners and project leads, it’s a constant battle.

But it shouldn’t be! It doesn’t have to be!

Let’s discuss the benefits of reviewing code, what it is, what it isn’t, and how to make it more than the blind rubber stamp approvals we’ve grown used to. I’ll show you my process and things that have helped me cultivate totally awesome code reviewers!

Kansas City. Lead Dev. She/Her. Physicist. Mentor. Mom. A Manager of Mischief. Dangerous in the front; deadly in the back. Enabler of repeatable, scalable success.

Rhia Dixon is a technical architect