Code reviews

Code reviews, often also called peer reviews, are a very powerful tool for developers’ daily work. We could almost say that they are fundamental, but the truth is that under certain conditions, it is possible to choose whether to perform them or not, provided, however, that if not, other methodologies are implemented. But let’s go in order and try to understand what a code review is.

A code review can be implemented in slightly different forms, but it typically consists of submitting a piece of code to one or more developers who did not write that code; these people are usually referred to as “reviewers.” So, for example, if you own a certain task and you developed the relative code, before deploying it in production (or usually even before merging your feature branch on your main branch, depending on your “framework”), your code is reviewed by some other teammate who did not write a single line of that code. The aim is not...