This Is Your Agent on Domain-Driven Design
In my experience using coding agents for more than a year, and Claude Code for 10 months, payoffs come from small, deliberate, incremental steps. On this journey, part of my challenge has been dealing with the low maturity of coding assistants—until very recently. Even with incredible advances in LLM capabilities, generating the domain model within a Domain-Driven Design context boundary is still quite disappointing. It's rarely better than unacceptable. Even when I provide significant guidance, the agent quickly and autonomously falls back to CRUD. In case you are unaware, CRUD is the opposite of a rich, behavioral, domain-driven software model.
It all comes down to the lack of well-designed domain models openly available for use as training data.
So, what's a poor software modeler to do? I'll share how I've overcome frustrating LLM limitations and constant rework using practical agent guidance that makes me smile.
Speakers
Vaughn Vernon is a software ecologist, architect, and modeler. As a leading expert in Domain-Driven Design and Event-Driven Architecture, Vaughn works with executive technologists, teams, and individual engineers, championing simplicity in the face of complexity. He helps teams and organizations optimize to realize business-driven and reactive systems as they transform from sprawling legacy systems. Vaughn is the author of four best-selling books and the curator and editor of his Addison-Wesley Vaughn Vernon Signature Series.