<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nullpointerexception on Devops Monk</title><link>https://devops-monk.com/tags/nullpointerexception/</link><description>Recent content in Nullpointerexception on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/nullpointerexception/index.xml" rel="self" type="application/rss+xml"/><item><title>Optional: Eliminating NullPointerException the Right Way</title><link>https://devops-monk.com/tutorials/java8/optional/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/java8/optional/</guid><description>The Problem Optional Solves NullPointerException is the most common runtime exception in Java. The root cause is that null is used for two different things simultaneously:
&amp;ldquo;This field has no value&amp;rdquo; (intentional absence) &amp;ldquo;This reference was never set&amp;rdquo; (programming error) Callers can&amp;rsquo;t tell which meaning applies without reading the documentation or source code. And nothing in the type system forces them to check.
// Java 7: what does null mean here?</description></item></channel></rss>