AI writes your code in seconds. Then you wait twenty minutes for CI to tell you whether it works. The bottleneck has moved: writing code is cheap, but verifying it - auditing AI-generated changes against a slow build - is now what stands between you and fast feedback.

This advanced talk shows how to cut Spring Boot build times drastically, often by 70% or more, so your pipeline gives answers in minutes instead of hours.

We'll work through the strategies that move the needle: parallel test execution, smart test slicing, reusing Spring application contexts, Testcontainers optimization, and build caching. For each, you'll see when it helps and how to measure the gain.

Just as important, we'll cover the pitfalls: the "optimizations" that quietly break test isolation, hide flakiness, or trade correctness for speed.

A fast build that lies to you is worse than a slow one.

This session assumes you already write tests and know your way around a CI pipeline. You'll leave with a concrete, prioritized checklist to take back to your own project and start reclaiming hours of feedback time.