As developers, we produce tons of code each day. We test our code, beautify it with code style scripts and finally verify using continuous integration commands, which control the integrity and cohesion of our solutions. Nevertheless, the true value of used code solution can be checked only by another developer, who knows the business domain, best practices, clean code principles and who may also have a different point of view from yours. In this article, I want to show you how code review can help you keep codebase in order and get more advantages for your team.

Let’s Do the Code Review

What exactly is code review? In simple words, you can explain it as reading your code by someone else. And that’s it.

One of the clean code principles is to write code that is readable for other human beings. Martin Fowler said:

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”

Code review is the first and critical check of this rule in real life. If your colleague cannot understand what you pushed to a repository, something went wrong.

Nowadays, you have tons of great tools to review your code, such as Github, Bitbucket, Gitlab and others. They feature a special UI, which lets you track changes and add comments in particular lines or even chars. In terms of usability, code review can be proceeded quickly and smoothly, even if your deadline is tight.

This is the preview of my article, published on Evojam’s blog. Read more here.