NullPointerExceptions have long been a source of frustration for Java developers, turning minor oversights into production issues. Null-safety in Java, however, is more than defensive coding—it reflects the language’s evolution toward expressing the absence of a reference more clearly. This session traces that journey from early practices like if (x != null) checks and the Null Object pattern, through annotations, Objects.requireNonNull, and design approaches such as using empty collections instead of null. It also explores how null-safety influenced API design, including the introduction of Optional and its role in making the Stream API more expressive.

Attendees will also learn how static analyzers, linters, and standards like JVerify help prevent unsafe code, and how upcoming JVM-level features in Project Valhalla aim to strengthen nullability guarantees. You will leave with a clear roadmap of how Java’s approach to null-safety has evolved, what tools and techniques are effective today, and what lies ahead for safer, more robust code.

What You Will Learn

• The historical evolution of null-safety in Java and its impact on language design

• Modern best practices for handling nulls using Optional, annotations, and static analysis

• What upcoming JVM-level changes such as Project Valhalla mean for the future of null-safety

Who Should Attend

Java developers, software engineers, and architects interested in writing safer, more maintainable Java code and understanding how null-safety continues to evolve in the platform.