Stop Using Lombok in Java. Seriously.🚫

Hi everybody 👋 Welcome back! Today we are going to discuss something that divides the Java world — Lombok. That magical little library some developers love … and others absolutely despise.

Now, I will spoil it for you from the beginning: I honestly believe you don’t have to use Lombok at all. 🙃

But hang on, before you throw tomatoes 🍅 at me, let me explain. Let’s break down what Lombok is and why people love it, why some people hate it and why I think you’re better off without it.

My articles are open to everyone; non-member readers can read the full article by clicking this link

If this article helped you, feel free to 👏 clap to help others discover this content, share with your fellow devs, and let me know your thoughts in the comments.

If you found this article helpful, consider supporting me with a coffee! Your support keeps me motivated to write more. ☕😊 Buy Me a Coffee

Image was generated. By AI

So… what exactly is Lombok? 🤔

Lombok is essentially a Java library to simplify the process of writing code, by omitting the need, for example, of getters/setters and constructors among others.

You know the drill — getters, setters, constructors, toString(), equals(), hashCode(), you know, the standard…