Do you know that too? You are working on Project A, which is still running on Java 11 LTS, while at the same time you are developing a new feature for Project B, which is already based on the current Java 21.

If you’ve been programming Java for a while, you probably use List, Set, and Map every day.

Hello everyone, In modern, microservices-oriented architectures, we want to keep components as independent as possible.

Hello everyone, If you’ve been around the Java world for a while, you know the picture: your code is littered with defensive queries like:

Hello everyone, In the world of Java development, we have become accustomed to rapid change.

Hello everyone, As developers, we know that writing an application is only half the battle.

Hello everyone, Java 8 fundamentally changed the way we write code.

Hello everyone, Today we’re diving into a Java topic that causes headaches for many developers, especially at the beginning: The Comparing strings using the == operator.

A few months ago I had a short discussion in a merge request with an experienced developer who asked me that’s why asked to undo my refactoring because == was easier to read.

Motivation Even in this day and age, when storage is comparatively cheap, it can still make sense to have it not to be wasted.