I am right there with you. I think people focus too much on the technical patterns from "DDD" like Aggregate, Entity vs Value, Repository, etc. The primary value of DDD is in modeling the software using the business's own terminology and boundaries. (You could look at it as a corollary of Conway's Law.) Implementing the technical patterns by themselves is complexity for no reason, but is the most common take-away from DDD. (I did this too for a time.) There is no specific set of technical patterns that will solve every business problem without actually learning about the business. "no silver bullet"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am right there with you. I think people focus too much on the technical patterns from "DDD" like Aggregate, Entity vs Value, Repository, etc. The primary value of DDD is in modeling the software using the business's own terminology and boundaries. (You could look at it as a corollary of Conway's Law.) Implementing the technical patterns by themselves is complexity for no reason, but is the most common take-away from DDD. (I did this too for a time.) There is no specific set of technical patterns that will solve every business problem without actually learning about the business. "no silver bullet"