<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lucien Immink on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/lucien-immink/</link><description>Recent content in Lucien Immink on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 04 Sep 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/lucien-immink/index.xml" rel="self" type="application/rss+xml"/><item><title>Design-first APIs for UI Components</title><link>https://javapro-en.svenruppert.com/design-first-apis-for-ui-components/</link><pubDate>Thu, 04 Sep 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/design-first-apis-for-ui-components/</guid><description>&lt;p&gt;Oh how the internet has changed. Where it began with HTML, static pages with minimal to no styling to a platform that can do almost everything we do with computers. Maps, games, productivity tooling and of course websites. They are all still presented using HTML, CSS and JavaScript.&lt;/p&gt;
&lt;p&gt;One major thing that did change is what kind of people are needed/working on these applications. Back- and front-end developers, designers, product owners, scrum masters, users, library owners, library consumers, framework authors. The list goes on and on. The reason is because the work became too big, too complex, for a single person to handle; at least in most enterprise areas.&lt;/p&gt;</description></item></channel></rss>