Neil Patrick Palanca

As a team lead, I strive to ensure that the whole team adheres to agreed upon best practices in their code. To spot systematic errors and issues that are hard to catch manually, my entire team relies on automated quality gates during the code review stage.

Here are my go to recommendations for code reviews that aren’t overbearing and help your team slow down – so they can speed up:

Shift left. Inspect your code with automated linters as early as possible, so that code issues are easier to fix. First, scan your code in real time with your IDE in my case, I rely on the PhpStorm checks. Next, push the code through the server side quality gate I prefer JetBrains Qodana to run more heavyweight checks, like vulnerability scanning or license auditing. Once the IDE and Qodana pre clear all of the issues, you can pass it on to the manual code review stage.
Shift from human to machine. From a cost efficiency perspective, it makes no sense for developers to spend their time doing manual cod