Uploaded April 2026 | Updated September 2026, 2 weeks ago
Sorry for the bad audio quality of this video due to a technical issue.
Sorry Lutske and Maarten
------------------------
Is your shiny new AI feature already tangled in a plate of spaghetti code, with helper classes sticking out like rogue meatballs and surprise side effects splattering everywhere? In this session, we follow a short story of a small chatbot named Leo that grows into a full‑blown platform, showing how careless choices turn neat experiments into costly traps. We then flip the script and refactor the same product into a scalable, enterprise-ready architecture using Clean Architecture. Drawing clear lines between domain, application, and infrastructure so that models can change without breaking everything else. By the end, you will see that good structure is not a luxury, but the only way to keep your AI moving fast without regrets.
What we cover
- The hidden cost of “just ship it” when models, data pipelines, and prompts keep changing
- Where Clean Architecture fits in a modern AI stack: domain, ports, adapters, and model gateways
- Demo: Route simple queries to a local LLM and advanced ones to the cloud, in minutes, not days.
- Pitfalls we hit in real projects and the patterns that saved us
What you will learn
- How to spot early signs of architectural decay in AI projects
- A step‑by‑step guide to isolating AI concerns from business rules
- Practical tips for introducing structure into an existing “AI spaghetti” codebase
Sorry for the bad audio quality of this video due to a technical issue.
Sorry Lutske and Maarten
------------------------
Is your shiny new AI feature already tangled in a plate of spaghetti code, with helper classes sticking out like rogue meatballs and surprise side effects splattering everywhere? In this session, we follow a short story of a small chatbot named Leo that grows into a full‑blown platform, showing how careless choices turn neat experiments into costly traps. We then flip the script and refactor the same product into a scalable, enterprise-ready architecture using Clean Architecture. Drawing clear lines between domain, application, and infrastructure so that models can change without breaking everything else. By the end, you will see that good structure is not a luxury, but the only way to keep your AI moving fast without regrets.
What we cover
- The hidden cost of “just ship it” when models, data pipelines, and prompts keep changing
- Where Clean Architecture fits in a modern AI stack: domain, ports, adapters, and model gateways
- Demo: Route simple queries to a local LLM and advanced ones to the cloud, in minutes, not days.
- Pitfalls we hit in real projects and the patterns that saved us
What you will learn
- How to spot early signs of architectural decay in AI projects
- A step‑by‑step guide to isolating AI concerns from business rules
- Practical tips for introducing structure into an existing “AI spaghetti” codebase
![[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.")
