Code reviews are necessary in a proper development workflow, but what happens when doing 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 with co-workers or show their coding "superiority". From my experience over the past 8 years to the stories my developer network shares, I know that code reviews can be a major pain point for many development teams.
But don't worry! It is possible to transform this pain point into a productive process! In this talk, I'll describe the common mistakes we make while performing a code review, the unwanted side effects those mistakes can cause, and suggest a few worthwhile solutions to these issues so that they are less likely to occur. By the end of this talk, development teams should be able to conduct code reviews fairly, catch substantiated mistakes, make productive suggestions, and still like each other afterward!