<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anshika Koul on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/anshika-koul/</link><description>Recent content in Anshika Koul on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 09 Jul 2026 10:01:52 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/anshika-koul/index.xml" rel="self" type="application/rss+xml"/><item><title>When Product Owners Commit Code: Small Steps, Big Impact</title><link>https://javapro-en.svenruppert.com/when-product-owners-commit-code-small-steps-big-impact/</link><pubDate>Thu, 09 Jul 2026 10:01:52 +0000</pubDate><guid>https://javapro-en.svenruppert.com/when-product-owners-commit-code-small-steps-big-impact/</guid><description>&lt;p&gt;&lt;em&gt;Disclaimer: No Product Owners were harmed in the making of this story.&lt;/em&gt;&lt;br&gt;
&lt;em&gt;Spoiler: They survived. In fact… they thrived.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We never planned to tell this story.. and certainly not six years later. Back when it happened, it didn’t feel revolutionary. It felt… practical. A small fix to a small annoyance. The sort of thing teams do every day just to make life a bit easier.&lt;/p&gt;
&lt;p&gt;But today, in a world where AI blurs boundaries and workflows become more fluid, the lesson behind this tiny experiment has become surprisingly relevant again. Because even before the age of “AI copilots”, our Product Owners had to leap across a much wider gap and yet what unfolded wasn’t about tools at all. It was about mindset. About curiosity. About empathy. And about what happens when teams stretch just a little bit beyond the edges of their roles.&lt;/p&gt;</description></item><item><title>Kotlin Multiplatform's Cross-Platform Brilliance at Norway's Nearly 400-Year-Old National Postal Service</title><link>https://javapro-en.svenruppert.com/kotlin-multiplatforms-cross-platform-brilliance-at-norways-nearly-400-year-old-national-postal-service/</link><pubDate>Thu, 01 May 2025 08:56:32 +0000</pubDate><guid>https://javapro-en.svenruppert.com/kotlin-multiplatforms-cross-platform-brilliance-at-norways-nearly-400-year-old-national-postal-service/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=nAkjwyQ8QOI&amp;amp;list=PLFeSAZzYdUodZjQy6a3pCBl43UUem8_E3&amp;amp;index=19"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2025/04/Magazin-Artikel-Banner-2-1024x214.jpg" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When we think of Norway’s National Postal Service, we think of legacy, tradition, and history – a service that has been delivering letters, packages, parcels, and sometimes even joy, for nearly 400 years.\&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
But what happens when such an ancient institution faces the modern challenges of software development and cross-platform integration? How does a company like Posten Bring navigate the world of fragmented business logic across multiple platforms and systems?&lt;br&gt;
&lt;br&gt;
But before I answer these questions, I want to ask &lt;strong&gt;YOU&lt;/strong&gt; - Have you ever had a complex business rule-set problem? You know the kind where you have business rules (logic) spread across multiple platforms, systems, and applications? Some of them might even be alter egos of the same rule hiding in different apps. You never know which one might turn up where; there is no single source of truth, solving errors takes hours of debugging, and making changes requires (oftentimes) painful coordination across teams and applications (ugh).&lt;br&gt;
&lt;br&gt;
We faced this exact challenge at Posten Bring As - Norwegian National Postal Service, founded way back in 1647 - a 378-year-old institution with software spanning more generations than most families! Our business logic was scattered across platforms, some of which were as ancient as the company itself (okay, maybe not that old, but close enough)!&lt;br&gt;
&lt;br&gt;
In this article, I’m spilling the tea. We will discover how the team at a century-old Norwegian postal services giant tackled modern challenges with cutting-edge technology.&lt;br&gt;
&lt;br&gt;
I’m going to walk you through our journey with Kotlin Multiplatform, including the hurdles we encountered, the lessons we learned, and why KMP is a game-changer for anyone grappling with similar challenges.&lt;br&gt;
&lt;br&gt;
This article is for you if troublesome &amp;amp; unruly business logic keeps you up at night &amp;amp; you want that to end NOW. It is also for you if you like to hear a good story.&lt;/p&gt;</description></item></channel></rss>