<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Process on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/process/</link><description>Recent content in Process on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Apr 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/process/index.xml" rel="self" type="application/rss+xml"/><item><title>Policy and Process: Thinking differently about Modern Java API design</title><link>https://javapro-en.svenruppert.com/policy-and-process-thinking-differently-about-modern-java-api-design/</link><pubDate>Wed, 30 Apr 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/policy-and-process-thinking-differently-about-modern-java-api-design/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=dT9Qog-g3Gw&amp;amp;list=PLFeSAZzYdUodZjQy6a3pCBl43UUem8_E3&amp;amp;index=18"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2025/03/Magazin-Artikel-Banner-2-1024x214.jpg" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There are many guides on achieving the right architectural balance and multiple thoughts about the ‘right’ way. In this article, I want to distil some of this thinking, apply it to Java API design, and use modern Java features. Historical patterns like AWT or RMI often influence older Java API design thinking, and it’s time to remind readers that modern Java features offer new, more powerful, and frequently safer ways to design APIs.&lt;/p&gt;</description></item></channel></rss>