<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sven Reinck on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/sven-reinck/</link><description>Recent content in Sven Reinck on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 10 Jun 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/sven-reinck/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond UML: Clean Software Architecture in the Age of AI‑Generated Code</title><link>https://javapro-en.svenruppert.com/beyond-uml-clean-software-architecture-in-the-age-of-aigenerated-code/</link><pubDate>Wed, 10 Jun 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/beyond-uml-clean-software-architecture-in-the-age-of-aigenerated-code/</guid><description>&lt;h2 id="abstract"&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Today we write more code in less time than ever before. AI systems act like permanently available junior programmers: They produce thousands of lines of code in minutes – but who takes responsibility for the software architecture?&lt;/p&gt;
&lt;p&gt;The real problem is therefore often not “bad AI code,” but the growing difficulty for people to keep an overview and make sound architectural decisions.&lt;/p&gt;
&lt;p&gt;This article discusses an idea for quickly building a mental model of existing code, spotting architectural problems early, and making targeted changes – without having to maintain static documentation in parallel.&lt;/p&gt;</description></item></channel></rss>