<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lutske de Leeuw on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/lutske-de-leeuw/</link><description>Recent content in Lutske de Leeuw on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 17 Apr 2026 07:00:03 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/lutske-de-leeuw/index.xml" rel="self" type="application/rss+xml"/><item><title>Java 26 Is Boring</title><link>https://javapro-en.svenruppert.com/java-26-is-boring/</link><pubDate>Fri, 17 Apr 2026 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-26-is-boring/</guid><description>&lt;h2 id="which-is-why-it-is-brilliant"&gt;Which Is Why It Is Brilliant&lt;/h2&gt;
&lt;p&gt;When people hear “boring tech”, they usually mean old, slow, or not innovative. But in production, boring implies something very different. Boring means predictable, with no surprises. Boring means your system still works at 3 a.m. when nobody wants to debug a memory leak. And boring also means that you can understand your system years after you wrote it.&lt;/p&gt;
&lt;p&gt;Many platforms try to impress developers with significant changes, shiny rewrites, or breaking updates. Java took another path. Java optimizes for trust.&lt;/p&gt;</description></item><item><title>AI without spaghetti: Clean architecture in the age of AI</title><link>https://javapro-en.svenruppert.com/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/</link><pubDate>Tue, 17 Mar 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/ai-without-spaghetti-clean-architecture-in-the-age-of-ai/</guid><description>&lt;p&gt;&lt;a href="https://schedule.jcon.one/2026/session/1052623"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2026/03/2026-Magazin-Artikel-Banner-1024x213.png" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="when-just-ship-it-turns-into-lasagna-code"&gt;When “Just ship it” turns into lasagna code&lt;/h2&gt;
&lt;p&gt;We start with a familiar scene: a small experiment that grows faster than its architecture can handle. This is exactly the kind of situation where clean architecture becomes essential. Like layering pasta without checking the recipe, we kept adding features until the structure began to wobble.&lt;/p&gt;
&lt;p&gt;At first everything seems perfectly reasonable. A quick integration with an API, a prompt that produces surprisingly good results. Suddenly the prototype starts solving real problems. The codebase grows organically: a helper class here, a service there.  Maybe a controller that does just a little bit more than it probably should.&lt;/p&gt;</description></item><item><title>Tame Your Llama: Run AI in Java</title><link>https://javapro-en.svenruppert.com/tame-your-llama-run-ai-in-java/</link><pubDate>Wed, 15 Oct 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/tame-your-llama-run-ai-in-java/</guid><description>&lt;p&gt;&lt;strong&gt;Introduction to AI in Java&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What is Llama?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Llama is an advanced open-source AI language model developed by Meta, designed for natural language understanding and generation. Unlike cloud-based AI models, Llama can be run locally, providing a powerful alternative for Java developers who want to integrate AI into their applications without relying on external services. The ability to run Llama models locally means developers can harness AI without exposing data to third-party providers, ensuring privacy and security.&lt;/p&gt;</description></item><item><title>Java 24: A Story of Code, Conflict, and Conquer</title><link>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</link><pubDate>Wed, 27 Aug 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</guid><description>&lt;p&gt;In a digital world far away from here, runs a Java application without problems. The logs are quiet, the servers are stable, and Emma and her team live in peace. But then, the first attack arrives! First innocent. A little spike in the memory use. But than another, and another. Within a couple of days, it turns into a disaster. Garbage collectors are going wild. The latency rises. The servers are shaking. The memory realm is flooded by invisible enemies: unnecessarily inflated object headers. They hide in every object, wasting valuable bytes and creating chaos in the heap.&lt;/p&gt;</description></item></channel></rss>