<?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://blog.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://blog.devops-monk.com/tags/nullpointerexception/index.xml" rel="self" type="application/rss+xml"/><item><title>Optional: Eliminating NullPointerException the Right Way</title><link>https://blog.devops-monk.com/tutorials/java8/optional/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/tutorials/java8/optional/</guid><description>The Problem Optional Solves NullPointerException is the most common runtime exception in Java, and it is almost always avoidable. Optional&amp;lt;T&amp;gt; is not a magic fix — used incorrectly it becomes a more verbose null check. Used correctly, it encodes the possibility of absence directly in the type system, so callers can never &amp;ldquo;forget&amp;rdquo; to handle the empty case. This article covers both how to use Optional and — critically — how not to.</description></item></channel></rss>