Which JVM Version are you using and why is it still Java 8?
summary
Many teams still run Java 8 not for technical reasons but because org process blocks simple upgrades; a proper pipeline lets a Dockerfile JVM bump be built, deployed and rolled back in minutes, ideally 5–8 minutes end-to-end. Real examples: Slack ships a prototype in about a week and validates with a 100k pilot, while some clients still expose an empty test folder and no CI. Practical fixes are trunk-based development, infra-as-code, platform teams, feature flags and small A/B-released MVPs that prove a JVM change quickly.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:15Can you upgrade your Java Version
- 3:30Why is it hard to upgrade
- 4:58How technologically capable is your organization
- 12:18Why should my organization do this
- 13:48Why do we do this
- 22:03Inverse Conway maneuver
- 26:08How can my organization be faster
- 31:21How can my developers be faster
- 37:13Experimenting
- 38:46Bootstrapping
- 39:40Reflecting
