On a recent project, a client had a very in-depth peer review system using a web based code review system called Gerrit. Gerrit works with GIT and prevents unauthorized developers to push changes into master Git repository. Instead, Gerrit provides a web based front-end that will only allow commits to be merged after it has been plus two'ed, or, in more human terms, when someone has OK'ed it to be merged. If the submitted code is not up to scratch, then it gets minus 1'ed and the submitter gets an email notification. On this particular project, because deadlines were pushed and to try and improve velocity, I became the hub of reviews for the rest of the team.
As a good few hours of everyday was spent reviewing, it led to creating a check list of things I look for when I’m doing code reviews and to talk about the best way I’ve found to approach them.
Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge