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 ain'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 native, Rhia Dixon is a lead software engineer at VMLY&R, a global agency focused on creating connected brand experiences. Primarily a backend dev, she creates software applications using Java, Python, Adobe Experience Manager, and a variety of other tech. While she has always been a STEM girl and holds a B.S. in Physics, her journey to the world of tech kicked off in the summer of 2017 during a full-stack web development bootcamp at the University of Kansas-Edwards Campus. Rhia has immersed herself in the KC tech community by volunteering -- both as a mentor, and as Diversity & Inclusion Director -- for Kansas City Women in Technology, a non-profit organization dedicated to bringing women in technology together and encouraging more women and girls to pursue careers in technology. When she’s not writing code or volunteering, Rhia is chasing her toddler, solving puzzles with her 1st grader, binge-watching Marvel movies, or spending time making memories with family and friends.