My journey with Domain-Driven Design began between two opposite extremes. As a structural engineer turned developer, I built applications where I was the domain expert. Then in my next role as a developer I implemented tickets without context, without customer feedback, and without any sense of the problem we were actually solving. I realized that this disconnect was even showing up in the code itself.

On a quest to find a balance, I found DDD.

Not knowing where to start, and not being in a position to apply higher-level patterns, I implemented every pattern at once, overwhelming both me and my team. The pattern that turned out to have the biggest impact was also the simplest one.

This talk walks you through that transformation, both in words and code, introducing tactical DDD concepts along the way.

Whether you're just discovering DDD or you've been circling it cautiously for a while, this is your invitation to stop waiting until you fully understand everything and just start. You'll leave with practical techniques you can apply tomorrow, honest pitfalls to watch out for, a path toward better collaboration and a more deliberate design.