#domaindrivendesign is overrated tilkov.com/post/2021/03/01/d…

I (respectfully) disagree with your article, or at least the implied premise. It suggests the DDD vocabulary requires experts or expertise, which implies that even using DDD language is a form of gatekeeping.

Depends on whether you’re talking about the DDD meta-language or a concrete, well-defined language for a particular domain. I have absolutely no problem with the latter, but I do have a problem with the expected ubiquity of the former :)

I'm in the opposite camp. The DDD language is a pattern language in the true sense, designed to _democratise_ the domain, in the same way Alexander's was intended to democratise architecture. It's a small, easy-to-learn vocabulary that enables enthusiasts to communicate.

I’m not sure I disagree. I am annoyed when it’s used to keep people out, or not as a means to an end, or as an excuse to stop thinking. Other than that, I am a fan and advocate its usage

Yes, I've come across people (usually Senior $adjective Architects) who look down their nose at people using the "wrong" DDD terms. I tend not too hang out with those people. But gatekeepers gonna gatekeep, whether it's DDD terminology or language snobbery.

I am assuming that your grouse is against the "looking down" part and not the drive to get to a "common vocabulary"?