<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spring on doismiu - dispatches from the infernal archive</title><link>https://doismiu.blog/tags/spring/</link><description>Recent content in Spring on doismiu - dispatches from the infernal archive</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 12 Dec 2025 00:00:00 +0100</lastBuildDate><atom:link href="https://doismiu.blog/tags/spring/index.xml" rel="self" type="application/rss+xml"/><item><title>The Kobayashi Maru of Java: Global Exception Handling</title><link>https://doismiu.blog/posts/the-kobayashi-maru-of-java/</link><pubDate>Fri, 12 Dec 2025 00:00:00 +0100</pubDate><guid>https://doismiu.blog/posts/the-kobayashi-maru-of-java/</guid><description>&lt;p&gt;For those who skipped the Starfleet Academy lectures, the &lt;a href="https://en.wikipedia.org/wiki/Kobayashi_Maru"&gt;&lt;strong&gt;Kobayashi Maru&lt;/strong&gt;&lt;/a&gt; is a training exercise designed as a &amp;ldquo;no-win scenario.&amp;rdquo; The goal isn&amp;rsquo;t to win, it&amp;rsquo;s to see how you handle inevitable failure. In the world of Backend Engineering, our no-win scenario is the &lt;strong&gt;Unhandled Exception&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;You spend weeks architecting a beautiful, clean service. You use Records, you optimize your SQL queries, you apply SOLID principles. And then, on production day, a user sends a malformed JSON, and your API vomits a 50-line Stack Trace directly into their browser console. It&amp;rsquo;s ugly, it&amp;rsquo;s unprofessional, and it exposes your internal logic to the world.&lt;/p&gt;</description></item></channel></rss>