DEV Community

Discussion on: Configure IntelliJ to show warnings for Lombok's @NonNull

siy profile image
Sergiy Yevtushenko

As mentioned in the article, this is a convention. To make it work it's enough to get rid of all explicit null values in code. This condition is much easier to check (search over all code). From my experience I can tell that not using null in code is an easy to get used to quite quickly.
With this convention nulls may appear only from external libs/code, but habit to create safety wrappers for such code also grows quickly. There is also similar approach to handling errors without using exceptions. Together these approaches result to concise, expressive and safe code, which is easy to write, read, test and maintain.