Often, implementing Domain-Driven Design (DDD) opens a can of worms. In this talk, we will share some of our own personal horror stories live. For instance, have you already encountered the Bounded Contexts (BC) vampire syndrome, where one BC is sucking all others BCs? The anemic mutation situation? The aggregate obsession? Or the Eventual Consistency Horizon?

Is DDD truly the source of some of our nightmares, or is there something more sinister lurking beneath the surface? Join us as we navigate the troubling landscape of software development, exploring the hidden biases and misconceptions that can haunt our projects.

Through our chilling experiences, we will challenge you to reconsider what you know about DDD and uncover the real culprits behind some of our production torments. This session is designed for advanced DDD practitioners and promises to be both enlightening and entertaining. Brace yourself and let’s unmask some hidden phantoms when developing software!

When building an Event Sourcing system, can we change the past? Can we also forecast “events” in the future?
If we want to provide various projections/visions of things that hapenned over the time, what are the consequences and trade-offs on our code?
All these questions will be answered during this talk. But moreover, I'll tell you our learning story about Bi-temporal Event Sourcing. Yet another illustration of the power of modeling, sketches and concrete examples when we need to understand each others.

Introduced by Eric Evans in 2004 via his Blue Book, Domain Driven Design (DDD) has received tremendous positive feedbacks from many developers & communities over the years. On the other hand, we have to admit that DDD has since not been widely used in the trenches or within most of our development projects... How can we explain such failure in its diffusion? Is DDD in itself difficult or is it just the way people used to present it which makes it hard to grasp and inaccessible?
Through our various (more or less successful ;-) experiences, we will try to highlight what DDD is using a simple and more accessible approach. The opportunity for us is to show you how helpful it can be for your day-to-day projects. Wouldn't be the perfect time for all of us to ease the DDD onboarding for beginners and to reboot DDD for experts?

Why we are still stuck with TDD nowadays? Through several facts & stories from the trenches, we will see why most of us still have not managed to grasp or to sustain the TDD experience.

Wouldn't be a good opportunity to meditate about how we are thinking? And why not, thinking outside of the box to get a better feeling of the TDD soul.