Episode 14

Your Spring Boot tests are passing, but can you trust them? This session reveals five critical mistakes that silently undermine your test suite's reliability and your confidence in deployments.

We'll tackle the tough questions: How can 100% coverage still miss critical bugs? Why is your test suite so slow? You'll see real tests that look correct but hide serious flaws - transaction rollback confusion, context pollution, and incorrect @SpringBootTest usage. We'll also sharpen your test strategy: picking the right test slice, reusing the application context, and slashing build times for faster feedback. Each pitfall comes with practical solutions and alternatives.

Through code examples and live debugging, you'll learn to write tests that actually catch bugs before production, shifting from hope to certainty. Perfect for developers burned by production issues despite "comprehensive" test suites. Joyful testing awaits!

Code was never the bottleneck — and AI just made that impossible to ignore. Writing code is now cheap, which changes everything except the code. This interactive session takes one uncomfortable claim seriously: good engineering practices don't die under AI, they get sorted.

Whatever was merely a proxy for "more code, faster" loses its justification. Whatever builds and carries an understanding of a system grows more valuable — because of AI, not despite it.

We'll trace this through three things every team wants right now: correct working code, costs under control, and enough experienced developers, with practical theories like Jevons' Paradox and Peter Naur's "Programming as Theory Building".

With interactive elements and concrete things you'll do differently on Monday.