Live data from Hacker News

DDD Is Overrated

tilkov.com

11–20 of 97 posts

Re: DDD Is Overrated

#11

Maybe update the title to "Domain Driven Design is Overrated", because this article has nothing to do with the Data Display Debugger.

Something tells me that in 2021 a lot more people will identify DDD to mean Domain-Driven Design than the concept that you mentioned

"man ddd" would disagree

speaking of which, ddd is the only application I have installed that relies on motif...

Re: DDD Is Overrated

#13

Maybe update the title to "Domain Driven Design is Overrated", because this article has nothing to do with the Data Display Debugger.

I was thinking of the debugger too. I was also surprised to see it described as “overrated” since it’s ratings have never been that good.

Re: DDD Is Overrated

#14
It was a great debugger in its time, with some unique features. True, its development was abandoned at long time ago, but saying that it is "overrated" seems a bit unfair.

Re: DDD Is Overrated

#16

It was a great debugger in its time, with some unique features. True, its development was abandoned at long time ago, but saying that it is "overrated" seems a bit unfair.

The article is about Domain Driven Delopment, not the ddd debugger.

Re: DDD Is Overrated

#17
post #9

If anything, i find that DDD is underrated and underused. But i can totally imagine projects where it goes completely over the top, like anything (frameworks, patterns, microservices, Redux -oh god Redux-, whatever) Happened the exact same thing with agility when it became Agile™

Sounds like the difference between agile and Agile. It helps to understand the domain when you're architecting a solution, but I didn't realise there was an extended nomenclature around it. I thought it was just a conceptual phrase.

Re: DDD Is Overrated

#19
Better article: https://dev.to/cheetah100/domain-driven-disaster-147i

The biggest flaw of DDD I've run into is there's no emphasis on when not to use it. There's no mention that over-coding business rules into modules and services locks you into businesses processes that are slow or impossible to update. There's no mention that most times you want to build services that offer platform capabilities, not focus on what "domain" they fall into. Nevermind that "domain" is basically undefined and can mean many different concepts and different types of concepts. DDD has some decent and good ideas, and is over extended to "this is how you should set up everything." Build more platforms where the domain logic exists in user land, not in code land. Everyone will be more productive for it.

The book Domain Driven Design is also terribly written. Good ideas written by someone who should not communicate with humans.

Re: DDD Is Overrated

#20
This article says nothing about DDD and all about how the author is coping with its gaining traction.

I myself find DDD a pilar I don't want to work with anymore.

Post reply on HN