Addressing this problem in the software field is a must... especially to mid/senior developers who want their codes to be reusable every time (which rarely or never does!).
And when one sees the general picture of DDD, it's all about fighting Template Driven Development.
Lead Developer and Solutions Architect, I specialise in Event Sourcing, DDD and Event Driven systems. PHP and GoLang developer. Enjoys being a smart ass and having a nice whiskey.
Location
Ireland
Education
MSc in Computer Science, Trinity College, Dublin
Work
Lead Developer and Solutions Architect at Contractor
You are completely correct, DDD helps us combat the idea of Template Driven Development. It comes at the problem from the opposite direction, putting the focus on the specifics of the Domain rather than generic patterns.
I think this is why so many people fall down when trying to apply DDD. They go into it and find the tactical patterns (VOs, entities, repos, etc...), which they then try to apply religiously, viewing them as templates for "good" system design. (I speak from experience here).
This is completely against DDD, which is about exploring concepts and language. The patterns are only really useful when they allow you to express the domain, otherwise they're just bloat.
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.
Thanks Barry for the nice read.
Addressing this problem in the software field is a must... especially to mid/senior developers who want their codes to be reusable every time (which rarely or never does!).
And when one sees the general picture of DDD, it's all about fighting Template Driven Development.
Thanks for the comment Yaser.
You are completely correct, DDD helps us combat the idea of Template Driven Development. It comes at the problem from the opposite direction, putting the focus on the specifics of the Domain rather than generic patterns.
I think this is why so many people fall down when trying to apply DDD. They go into it and find the tactical patterns (VOs, entities, repos, etc...), which they then try to apply religiously, viewing them as templates for "good" system design. (I speak from experience here).
This is completely against DDD, which is about exploring concepts and language. The patterns are only really useful when they allow you to express the domain, otherwise they're just bloat.