I'm a software developer turned trainer and consultant, passionate about helping teams build software that truly serves their business. For over 15 years, I've been exploring, practicing, and teaching Domain-Driven Design.
My journey began in healthcare software, where I first discovered how critical it is for software to accurately reflect the complex realities of a business domain. This experience shaped my belief that great software starts with deep understanding.
Started programming as a teenager, fascinated by the ability to create something from nothing. That curiosity never left, it just evolved into a deeper question: how do we build software that actually matters?
Working on healthcare systems taught me that the biggest challenge isn't technology, it's understanding. Medical domains are complex, regulated, and life-critical. This is where I first grasped the value of Domain-Driven Design.
Eric Evans' "Blue Book" was a revelation. Here was a systematic approach to the problems I'd been struggling with. I dove deep, experimented, failed, learned, and eventually became a practitioner and teacher.
Realizing that knowledge multiplies when shared, I began training teams and speaking at conferences. Each workshop teaches me as much as the participants, each domain reveals new patterns and insights.
Now I combine years of hands-on experience with the latest developments, including LLM-assisted development. The core principles remain, but the tools and techniques keep evolving. So do I.
Technologies come and go. Frameworks rise and fall. But the principles of good software design endure. That's what I teach.
I don't teach "how to use framework X." I teach the underlying principles that help you make good decisions regardless of your tech stack. When you understand the "why," the "how" becomes clear.
Reading about DDD is one thing. Applying it is another. My workshops are hands-on, using real exercises and collaborative modeling sessions. You learn by doing, not just listening.
The best domain knowledge lives in people's heads, not documents. Techniques like EventStorming bring experts together to externalize and share that knowledge in ways documents never could.
The DDD community is generous and collaborative. I'm proud to contribute to its growth.
Co-organizing this Berlin-based conference has been a highlight. Bringing together practitioners from around the world to share experiences, challenge assumptions, and learn from each other.
kandddinsky.deCo-founding Virtual DDD means DDD knowledge is accessible to everyone, everywhere. Regular online sessions, a welcoming community, and the chance to learn from experts across the globe.
virtualddd.comHelping grow the local DDD scene in Germany through meetups, workshops, and conversations. Great to see more teams adopting these practices.
Get InvolvedTeaching is great, but I still love building things. These side projects keep me sharp and grounded in the realities of software development.
A roguelike game project that lets me experiment with event sourcing patterns in a fun context. Building games is a great way to explore complex state management challenges.
Another creative project where I get to apply DDD principles outside of enterprise software. Because domain modeling works everywhere there's complexity to manage.
Whether you need training for your team, help with a complex domain, or just want to chat about DDD, I'd love to hear from you.