DDD is incredibly helpful but insanely complex to both understand and implement.
LLMs can make building and implementing DDD quicker but it will make understanding even more complex.
IMHO, the best place for DDD is a big ball of mud that works but an absolute pain to deal with - refactoring that using DDD is the right place for it. You have both a business and software that "works" - the software now needs improvement. As opposed to a person or team beginning with DDD from scratch because it's "better for the long run".
Yes, a person or team who understands DDD well will have an edge in the age of AI but technical competency at a company is rarely the reason for its success (or failure) in the first place - it's just a lever.
DDD is incredibly helpful but insanely complex to both understand and implement.
LLMs can make building and implementing DDD quicker but it will make understanding even more complex.
IMHO, the best place for DDD is a big ball of mud that works but an absolute pain to deal with - refactoring that using DDD is the right place for it. You have both a business and software that "works" - the software now needs improvement. As opposed to a person or team beginning with DDD from scratch because it's "better for the long run".
Yes, a person or team who understands DDD well will have an edge in the age of AI but technical competency at a company is rarely the reason for its success (or failure) in the first place - it's just a lever.
> the best place for DDD is a big ball of mud that works but an absolute pain to deal with
So a vibe-coded codebase?