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
Painful days wasted optimizing the wrong part of the code... Blind attempts to fix a production performance issue. Then, speculative “micro-optimizations" that clutter the code for no measurable gain. Only to later trace the problem to the most unexpected cause. This talk explains how to efficiently zoom in on a performance bottleneck using OpenTelemetry distributed tracing, metrics, and execution profiling. After we learn to read a flame graph, we’ll trace typical backend bottlenecks, such as resource starvation (threads and JDBC Connections), time-consuming interceptors, repeated network calls, CPU hotspots, and lock contention, using a variety of mainstream tools. Join this session to prepare for the performance issues that any successful application will eventually have.
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
Painful days wasted optimizing the wrong part of the code... Blind attempts to fix a production performance issue. Then, speculative “micro-optimizations" that clutter the code for no measurable gain. Only to later trace the problem to the most unexpected cause. This talk explains how to efficiently zoom in on a performance bottleneck using OpenTelemetry distributed tracing, metrics, and execution profiling. After we learn to read a flame graph, we’ll trace typical backend bottlenecks, such as resource starvation (threads and JDBC Connections), time-consuming interceptors, repeated network calls, CPU hotspots, and lock contention, using a variety of mainstream tools. Join this session to prepare for the performance issues that any successful application will eventually have.





![[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. [VDBUH2026] Sander Hoogendoorn - Keynote: Seven Habits of a (Mostly) Successful Team](https://i.ytimg.com/vi/8pDCcKqbwB4/mqdefault.jpg)




