<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SOFTWARE DEVELOPMENT on Flowing Code</title><link>https://www.flowingcode.com/en/tag/software-development/</link><description>Recent content in SOFTWARE DEVELOPMENT on Flowing Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 21 Jul 2026 13:41:49 +0000</lastBuildDate><atom:link href="https://www.flowingcode.com/en/tag/software-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Vaadin Add-on in Record Time with Claude AI</title><link>https://www.flowingcode.com/en/building-a-vaadin-add-on-in-record-time-with-claude-ai/</link><pubDate>Tue, 21 Jul 2026 13:39:02 +0000</pubDate><guid>https://www.flowingcode.com/en/building-a-vaadin-add-on-in-record-time-with-claude-ai/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-2391" height="559" loading="lazy" src="https://www.flowingcode.com/images/uploads/2026/06/relative-time-blog-post-1024x559.jpg" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">Not long ago, I shared my experience on &lt;a href="https://www.flowingcode.com/en/vaadin-10-to-25-migrating-a-8-year-old-app-with-claude-ai/">how to migrate a legacy Vaadin application with the help of Claude AI&lt;/a>. That experience proved that AI is fantastic for untangling legacy code, but it left me with a new question: &lt;strong>What happens when we start from scratch?&lt;/strong> Recently, my team at Flowing Code proposed creating a new add-on: a Vaadin wrapper around the &lt;code>&lt;a href="https://github.com/github/relative-time-element">@github/relative-time-element&lt;/a>&lt;/code> component. This time, I decided to keep Claude in the loop from minute zero, not just as a code generator, but as an architectural design partner.&lt;/p></description></item><item><title>Why Vaadin Still Matters in 2026</title><link>https://www.flowingcode.com/en/why-vaadin-still-matters-in-2026/</link><pubDate>Tue, 30 Jun 2026 13:40:16 +0000</pubDate><guid>https://www.flowingcode.com/en/why-vaadin-still-matters-in-2026/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-2335" height="572" loading="lazy" src="https://www.flowingcode.com/images/uploads/2026/06/Why_vaadin_still_matters_2026-1024x572.jpg" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">In an industry obsessed with the new and shiny, asking why a technology continues to thrive can be more interesting than asking what will replace it next.&lt;/p>
&lt;p class="wp-block-paragraph">&lt;a href="https://vaadin.com/">Vaadin&lt;/a> is not a newcomer. Its development started in the early 2000s, and it became open source in 2002. Over the years, it has gone through several major architectural changes while remaining actively developed and widely used in enterprise applications. In a space where frameworks often come and go within a few years, that alone makes Vaadin worth reflecting on.&lt;/p></description></item><item><title>Vaadin 10 to 25: Migrating a 8-Year-Old App with Claude AI</title><link>https://www.flowingcode.com/en/vaadin-10-to-25-migrating-a-8-year-old-app-with-claude-ai/</link><pubDate>Thu, 18 Jun 2026 19:49:25 +0000</pubDate><guid>https://www.flowingcode.com/en/vaadin-10-to-25-migrating-a-8-year-old-app-with-claude-ai/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-2281" height="572" loading="lazy" src="https://www.flowingcode.com/images/uploads/2026/06/global-stats-2026-1024x572.jpg" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">Back in 2018, &lt;a href="https://www.flowingcode.com/en/vaadin-10-spring-demo-application-world-cup-rusia-2018-stats/">our team at Flowing Code built a quick, scrappy demo to show off the then-brand-new Vaadin 10&lt;/a>. It was a hackathon project built around the major global football tournament happening in Russia at the time. The app was designed as a live dashboard tracking match fixtures, real-time scores, and group standings.&lt;/p></description></item><item><title>Time &amp; Material vs Fixed Price? Why We Prefer the Flexible Approach</title><link>https://www.flowingcode.com/en/time-material-vs-fixed-price-why-we-prefer-the-flexible-approach/</link><pubDate>Mon, 10 Jun 2024 13:55:09 +0000</pubDate><guid>https://www.flowingcode.com/en/time-material-vs-fixed-price-why-we-prefer-the-flexible-approach/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-1580" height="510" loading="lazy" src="https://www.flowingcode.com/images/uploads/2024/04/image-20-1024x510.png" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">When it comes to &lt;a href="https://en.wikipedia.org/wiki/Software_development" rel="noreferrer noopener nofollow" target="_blank">software development&lt;/a> contracts, businesses typically face a choice between two common pricing models: time and material, and fixed price. These frameworks offer distinct approaches to budgeting, project scope, and risk management. In this blog post, we’ll explore the differences between these two models, outlining their respective advantages and drawbacks. This discussion will help clarify why our company has chosen the time and material approach and offer insights into how it aligns with our business values and project management style. Stay tuned as we delve into the nuances of these pricing strategies and share the reasons behind our decision.&lt;/p></description></item></channel></rss>