The Async Code Review
Today we’ll talk about one of the central pieces of the everyday work of Software Engineers, the Code Reviews. As you already noticed I’m a strong advocate of asynchronism and not only when we talk about code development.
Usually in these modern days of Software Development when we finish some new implementation the next step submit that code for a peer review by opening a new merge request (depending on your source control manager).
As many of you already know, Code Reviews are a quality assurance activity that consists of the validation of source code modifications by others. Through the Code Reviews, we can achieve better code quality, finding bugs early in the development process, knowledge sharing, among others vast benefits.
I love Code Reviews and I have learned a lot doing code reviews and having my own code reviewed by my teammates. Good Code Reviews aren’t easy to do, a good Code Review must have a deep commitment to the code we are reviewing in order to validate higher abstractions such as the design of the solution, corner cases that can be hiding, a good code review goes further from just reviewing code style, naming, and indentation.
