Code Review Like You Mean It

Building a solid development workflow is very different now than it was a few years ago¹. The biggest improvements of workflow and the increase in quality is probably due to the concept of pull requests², which has made code collaboration explode thanks to the decreased friction that goes into contributing to a project.

This article describe how to properly do code reviews and working with pull requests. Having a focus not solely on finding errors, but using it as a tool for learning and sharing knowledge, as well as for building a common code quality and coding style for an entire project, spanning all involved authors.

Basically before GitHub. ↩
Called Merge requests in Gitlab and is basically a request to merge a branch back to the master branch, and has social aspects such as discussions and inline comments, perfect for code reviews. ↩