Uploaded April 2026 | Updated September 2026, 2 weeks ago
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
Let's explore memory leaks and memory inefficiency patterns in Java backend systems. After reviewing the Java Memory Model and the JVM flags you #musthave in production, we’ll analyze heapdumps of 10 common memory leaks, collected with ❤️ from 150+ companies over a decade of consultancy. You'll hear about ThreadLocal, inner classes, cache/hash keys messup, thread leaks, and many others. In the end, you'll get access to a large repo of memory leaks + heap dumps for later self-study. Oh, and you can get a bounty for any real memory leak you had, which is not yet in that repo 😊.
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
Let's explore memory leaks and memory inefficiency patterns in Java backend systems. After reviewing the Java Memory Model and the JVM flags you #musthave in production, we’ll analyze heapdumps of 10 common memory leaks, collected with ❤️ from 150+ companies over a decade of consultancy. You'll hear about ThreadLocal, inner classes, cache/hash keys messup, thread leaks, and many others. In the end, you'll get access to a large repo of memory leaks + heap dumps for later self-study. Oh, and you can get a bounty for any real memory leak you had, which is not yet in that repo 😊.
![[VDBUH2026] Sander Hoogendoorn - Keynote: Seven Habits of a (Mostly) Successful Team](https://i.ytimg.com/vi/8pDCcKqbwB4/mqdefault.jpg "[VDBUH2026] Sander Hoogendoorn - Keynote: Seven Habits of a (Mostly) Successful Team
After four years of building, breaking, and learning at iBOOD, we’ve discovered what makes a development team truly successful. No frameworks, no dogma—just seven practical habits that help teams ship great software, stay motivated, and keep improving.
This talk is based on real experiences, not theory, nor agile BS. We’ll dive into:
Prioritizing Pragmatically Balancing business needs, technical debt, and innovation.
Killing Complexity Keeping architecture, code, and processes simple, even as you scale.
Owning the Work Why autonomy beats process, and how teams can take real ownership.
Communicating Relentlessly Why constant, transparent communication makes everything smoother.
Building Microteams Why smaller, focused teams move faster and collaborate better.
Delivering Continuously Making small, frequent releases a habit (without the chaos).
Having Fun Because happy teams build better software. An afterthought about purpose, mastery, and autonomy.
I’ll share stories from the trenches—what worked, what failed, and what we’d never do again. If you’ve ever wondered how to build a team that doesn’t just survive but thrives, this talk will give you concrete ideas to take back to your team.")
