DEV Community

loading...

Discussion on: The Concept of Domain-Driven Design Explained

Collapse
royshouvik profile image
Comment marked as low quality/non-constructive by the community. View Code of Conduct
Shouvik Roy

It is evident from the content of the article that the author has no real experience with development let alone domain driven design. There are far too many meaningless sentences to point out. This was clearly written as a marketing activity and should not be considered a technically accurate piece.

Collapse
rrei profile image
Comment marked as low quality/non-constructive by the community. View Code of Conduct
Rui Rei

Sick of this marketing bullshit. No meaningful content whatsoever... "DDD is great because it solves all your problems by getting rid of complexity and solving all your problems and making everything better. Just like my post, buy this course and you'll be all set to become a DDD Master Ninja. Programs will start writing themselves afterwards, or you'll get your moneyz back."

Collapse
raddevus profile image
raddevus

I stared at the 3rd sentence just trying to make sense of it...
" They can be developed and easily maintained individually, after what they are joint in a complex application."
Tried to read more but much of it sounded like that.