Eugene Fedorenko is Designing, Writing, Reading, and Traveling

Code review workflows

Published at Beanstalk

Early last year the Beanstalk team started an internal conversation on the best ways for a private team to control code quality and minimize the chance of breaking production code with a “bad" commit. As a small team of developers we are not used to formal processes, so the most natural thing was to see what bigger teams do. I started researching code review processes and tools in various companies and was astonished by how different they can be. In retrospect it makes sense — software built for NASA has a much smaller right for an error than an open source experiment built on the side. Here are a few cases I found the most interesting: