<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vauban Vincent on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/vauban-vincent/</link><description>Recent content in Vauban Vincent on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 13 Mar 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/vauban-vincent/index.xml" rel="self" type="application/rss+xml"/><item><title>Java 26 + Spring Boot 4: From Certification Skills to Production-Ready Apps</title><link>https://javapro-en.svenruppert.com/java-26-spring-boot-4-from-certification-skills-to-production-ready-apps/</link><pubDate>Fri, 13 Mar 2026 07:00:00 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-26-spring-boot-4-from-certification-skills-to-production-ready-apps/</guid><description>Most Spring developers don’t fail in production because they forgot an annotation. They fail because the “non-feature” parts of the system were treated as optional: observability that comes too late, security added at the end, data access built under deadline pressure, APIs that can’t evolve without breaking clients, tests that don’t protect upgrades. This article argues that Spring certification</description></item></channel></rss>