Why DDD Matters More in the Age of AI-Generated Code
Generated code is cheap. Domain clarity is scarce.
Series
Domain-Driven AI
A series about why domain-driven design becomes more important in the age of AI-generated code, not less.
Posts in this series
More Material Is Not Better Context
Most discussions about context for AI-assisted development focus on how to give the model more relevant material. Larger context windows help. Better retrieval helps. So does adding the file, ticket o
AI Should Not Become the Source of Truth
Most discussion about AI-generated documentation focuses on accuracy. Can the model find the right information? Does it hallucinate? Can its answer be verified? Those concerns matter, but I have becom
Contracts Are Where Context Becomes Visible
Most writing about bounded contexts pays close attention to what happens inside the boundary. The model should use the language of the domain. Business rules should have a clear home. Concepts that me
Internal, External, and Contract Models Should Not Be the Same Thing
Discussions about model separation often end up being discussions about boilerplate. One object arrives at a service boundary, most of its fields are copied into another object, and a similar conversi
AI-assisted development needs boundaries
Most writing about AI-assisted development seems to settle into three positions. There is the productivity account, where an agent is judged by how quickly it turns a ticket into code, the prompting a
