why keeping Java and Spring current matters more in the AI era.

Java ships a new release every six months, Spring Boot runs on its own cadence and AI is generating code faster than most teams can review it. For enterprise developers, that raises a real question: how do you keep pace without breaking what already works? In a recent Randstad live session, Broadcom Spring developer advocates Dan Vega and DaShaun Carter unpacked what's actually happening in Java right now, and why upgrades, AI and security have become one conversation.
Vega's take on the release cycle is refreshingly practical. Teams don't need a new JDK the day it lands, but they do need a plan, because without one the upgrade never fits the budget. Smaller releases are easier to adopt, and staying current brings performance and security fixes for free. Carter runs most of his AI work on off-the-shelf models with what he calls "Raspberry Pi money." He says the mistake those models make most is not knowing the latest version of Java or Spring. His fix: set the context first and point the model to the docs. Vega also pushed back on the idea that AI belongs in Python. Most application developers now consume large language models through a REST endpoint, he argued, so building generative AI into an existing Java app beats replatforming the whole team.
The bigger story is maintenance. AI is putting more software into production and helping attackers chain low-severity vulnerabilities into serious ones. The Spring team went from an average of 6.4 reported vulnerabilities a month to 422 in April alone. Watch the full conversation for their take on Spring Boot 4, options for teams stuck on older versions and why Carter's motto for every live session is "don't leave hungry."
This article was developed from a transcript of a Randstad virtual event.



