The articles in this series about being an effective code reviewer have be leading to this final article on imposter syndrome. Sending your code for review or reviewing the code of a colleague can be intimidating and stress inducing. Often you feel as though, I am not qualified to do…

Code reviews can often be a source of stress and frustration and they should not be. From my original article that defined code review and their benefits: #1 rule: This is about sharing knowledge and improving, not to catch someone out or shame them. Code reviews are one of the…

Type of code reviews There are several types of code reviews and you may want to adjust your style depending on the type of review you are undertaking: Features Bug fixes Other: script to automate a recurring task, github template, … Features Features are more likely to come to you in a series of code…

The worst case scenario for a peer code review is when each developer thinks the other will look at the code closely. This happens in real life, more often than you would think. How do you go about ensuring this does not occur? …

A code review is a standard practice in the software development life cycle, where one or more people review the source code of another developer. The goal of the review can vary, but it is generally to increase the code quality and provide consistency to a code base. It is…