How does authentication work? How can it be implemented securely? Who saves sessions? How long do they last? These are questions I get asked a lot, and I hope to answer them comprehensively in this post.

Some sentences get repeated so often they become boring clichés, you know? Well, in the world of developers, there was “generative AI is an accelerator” or “It’s a multiplier, if the value is zero, the result is zero.”

AI Revolution? Will an LLM steal my job? Here’s what has really changed in my work since artificial intelligence began to be used at scale.

Let’s start by saying that the code review is a tailor-made suit and not a one-size-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 told you 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.