Author talks about how DDD is overrated and gives a couple of arguments about nomenclature. The real issue seems to be in plain sight in the article: > But I’

Author talks about how DDD is overrated and gives a couple of arguments about nomenclature. The real issue seems to be in plain sight in the article: > But I’m annoyed by the fact that recently, it seems that any time somebody talks about how to architect system or service boundaries, or even just mentions non-technical design, everybody feels compelled to bring in the DDD experts That's the issue, their own experience has been terrible but I don't see any specifics about why domain driven design is terrible. Provide an example. Go through the rigor of your arguments. Show us some code, something concrete, tell us a story about how it was painful to them and what was the impact - whatever is needed to make a strong argument. The problem with articles like this is people read up on it, make their mind, and now you have a sloth of people converted to "Anti-DDD religion" will become painful to deal with at work because they read up some HN article about how DDD is overrated. It gets stuck in their minds like cereal in an empty milk bowl. I expect more from the author after saying "There, I said it." Totally ok to be anti-DDD, would love to hear more though.