Code reviews are a must in a proper development workflow, but what happens when performing or receiving one becomes as fun as getting a root canal? Instead of contributing meaningful suggestions, developers often use these reviews as an opportunity to rehash old arguments or show their "superiority".
From personal experience as a software engineer over the past 8 years to the stories my professional network shares, I know that code reviews can be a major pain point for many development teams.
In this talk, I'll describe the common mistakes we make while performing a code review and how it can cause unwanted side effects among a team and their codebase. I'll also describe worthwhile solutions to these issues so that they are less likely to occur. By the end of this talk, dev teams should be able to conduct code reviews fairly, catch substantiated mistakes, make productive suggestions, and still like each other afterward!
After almost 8 years in the software engineering industry, she has worked in various industries like higher education and healthcare as well as several Las Vegas startups. Currently, she is a software engineer in the FinTech industry where she continues to solve complex problems to help modernize the FinTech space.
Any remaining time she has not advancing her career is dedicated to educating, mentoring, and leading new software engineers. From her #DontBeAfraidOfTheTerminal series on Instagram to her lessons and talks as a Code.org volunteer for Las Vegas, Adrienne wants to share her knowledge with everyone and help anyone truly curious to become knowledge leaders. She strongly advocates for STEM education and always encourages young women and girls to explore a career in software engineering.
And for the important information: her favorite PC/video games are Age of Empires II, RollerCoaster Tycoon 2, and the Borderlands series; her favorite lipstick color is Bite's Aubergine; her favorite movies are Inception (really, anything be Christopher Nolan) and The Matrix.