Monthly Archive: April 2019

Code reviews are a common part of most development teams workflow these days and for good reason. Code reviews give us a process of keeping code quality high, sharing knowledge. catching mistakes and keeping a consistent code base. If you use git, you probably already heard about pull-requests, which basically is a merge request with a code review requirement. I help teams learn to conduct productive and positive code reviews, so the process becomes an enjoyable part of their development life-cycle. Here are my 10 tips for conducting a productive and positive code review, that gives value to both the reviewer and the author(s). 1. Figure out what the goal of the code review is Something that often happens in teams that are new to code reviews, is that the...