Let’s start by saying that the code review is a tailor-made suit and not a one fits all. What to report and what to ignore depends on the needs of the project and the level of the developer who submitted the code.

A few months ago everyone updated their job title on LinkedIn to AI Expert, there are now more AI experts than CEOs in my own company. Ok, I’m not an expert at all, I’ve done some experiments on chatGPT and I have many doubts.

Let’s be honest, as developers we are annoyed by people who test our code and find dozens of errors. I get it but good QA engineers really save our asses, be kind to them.

“What the fuck code is this? I’ve said a thousand times to use strict operators, you don’t care about the quality of the project!” If you find yourself thinking things like that when doing code reviews this post is for you.

What does pixel perfect mean? In frontend development slang, a web page perfectly identical (to the pixel) to the design provided is called pixel perfect.

We all know that naming things takes more time than coding. Here are the ten worst common names to give to your files, variables, classes…

I stare down until the code confesses.