Code reviews are a must in a proper development workflow, but what happens when performing or receiving one is as pleasant 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 developer over the past 8 years to the stories my developer network shares, I know that code reviews can be a 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!
👋 ABOUT ADRIENNE 👋
Currently a Senior Developer Advocate for MongoDB, Adrienne Tacke is also a Filipina software engineer, speaker, published author of the book Coding for Kids: Python, and a LinkedIn Learning instructor who specializes in Cloud Development courses. Perhaps most important, however, is that she spends way too much money on desserts and ungodly amounts of time playing Cyberpunk 2077.
