Java coding hacks developers should know 🧵 1) Use Map.ofEntries() for creating multi-pair immutable maps Why: Shorter, immutable, safer and avoids accidental mutation.

theskilledcoder's tweet image. Java coding hacks developers should know 🧵

1)  Use Map.ofEntries() for creating multi-pair immutable maps
Why:  Shorter, immutable, safer and  avoids accidental mutation.

2) Use Optional. map().orElse() instead of manual null handling Why: Eliminates null checks, reads better, and chains smoothly with other logic.

theskilledcoder's tweet image. 2) Use Optional. map().orElse() instead of manual null handling
Why: Eliminates null checks, reads better, and chains smoothly with other logic.

3) Use Enum.valueOf() + name() for safe enum conversion Why: Cleaner, and lets you easily serialize/deserialize enums in APIs, DB, or files.

theskilledcoder's tweet image. 3) Use Enum.valueOf() + name() for safe enum conversion
Why: Cleaner, and lets you easily serialize/deserialize enums in APIs, DB, or files.

4) Use Comparator.comparing().thenComparing() instead of custom logic Why: Clear, readable, no error-prone conditional comparisons

theskilledcoder's tweet image. 4) Use Comparator.comparing().thenComparing() instead of custom logic
Why: Clear, readable, no error-prone conditional comparisons

5) Use Optional.ifPresentOrElse() instead of if-else with isPresent() Why: Cleaner and more expressive - no more manual get() calls or if-else clutter.

theskilledcoder's tweet image. 5) Use Optional.ifPresentOrElse() instead of if-else with isPresent()
Why: Cleaner and more expressive - no more manual get() calls or if-else clutter.

The first seems more readable!


This is not the goal of Optional, which is a data wrapper not a control flow operator. When implementing an algorithm it is better to write a null check with a simple if than using an Optional.


"Use Optional. map().orElse() instead of manual null handling" Nah, that is actually not recommended. Only use Optional if you receive an Optional.


Not sure you should do this just because it compiles/works. I like your other examples though!


Sorry, it's a bad pattern. You should use it only if you already got an optional User. Otherwise use ? operator as it is cleaner, concise with no overhead. Even if you need chaining - there's a better way by using instanceof with patterns:

AlloyLauncher's tweet image. Sorry, it's a bad pattern. You should use it only if you already got an optional User. Otherwise use ? operator as it is cleaner, concise with no overhead. Even if you need chaining - there's a better way by using instanceof with patterns:

United States Trends
Loading...

Something went wrong.


Something went wrong.