<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CodeScene on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/codescene/</link><description>Recent content in CodeScene on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 21 Oct 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/codescene/index.xml" rel="self" type="application/rss+xml"/><item><title>Map your Code - Master your Architecture</title><link>https://javapro-en.svenruppert.com/map-your-code-master-your-architecture/</link><pubDate>Tue, 21 Oct 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/map-your-code-master-your-architecture/</guid><description>&lt;p&gt;In projects with hundreds of thousands of lines, it is easy to lose track of code, architecture and quality. Are we still on the right track, are we blocking ourselves with internal dependencies, or are we already stuck? Software is immaterial; we cannot see how it is doing.&lt;/p&gt;
&lt;p&gt;To know how our software is doing, we have systematically check if the mental models of the developers matches the written code. Spoiler, they do not, as software changes too fast to keep track, every developer has their own model and no one has the complete picture.&lt;/p&gt;</description></item></channel></rss>