Why NullPointerExceptions Still Haunt Java Developers—and How to Defeat Them

Origin of Null Pointers

Null references were introduced by Tony Hoare in 1965 when designing ALGOL 60, and later adopted by many languages such as C, C++, C#, Go, while languages like Rust avoid them. Hoare later called the null reference “the billion‑dollar mistake”.

Since JDK 14, NPE messages include more context, e.g.:

Cannot invoke "String.length()" because "s" is null

How to Deal with Null Pointers

Defensive programming helps prevent NullPointerExceptions.

1. Proactively check for null. Example:

public static boolean isEmpty(CharSequence cs) {
    return cs == null || cs.length() == 0;
}

Many utility libraries provide isEmpty, isNotEmpty, isNotBlank, or CollectionUtil.isEmpty methods.

2. Avoid returning null. Return an empty collection or optional instead of null.

3. Throw an exception when appropriate. Providing a clear exception is better than returning null.

Traditional nested null checks can become verbose:

public static String getUserOrderDetail(Integer userId) {
    User user = User.getUser(userId);
    if (user != null) {
        Order order = user.getOrder();
        if (order != null) {
            Address address = order.getAddress();
            if (address != null) {
                String detail = address.getDetail();
                if (detail != null) {
                    return detail;
                }
            }
        }
    }
    return "Sorry, not found";
}

Java 8’s Optional simplifies the flow:

public static String getUserOrderDetail(Integer userId) {
    return Optional.ofNullable(User.getUser(userId))
        .map(User::getOrder)
        .map(Order::getAddress)
        .map(Address::getDetail)
        .orElse("Sorry, not found");
}