3 ms·
The main point is that language you use to talk business should be used to write code. I don't get how using ubiquitous language can slow down the projects. >
by loziuu 4y ago
The main point is that language you use to talk business should be used to write code. I don't get how using ubiquitous language can slow down the projects.
> clear domain language that can be shared with the business
It does not work like that. Business share their lanaguage with you, not other way around.
Most important thing in DDD is Domain Expert. He's the cental point of strategic DDD. If you don't have one, then you either have CRUD app (which you shouldn't use DDD for - stick with ADM) or you can just use something called "DDD Lite" which is often referred to as "OOP done right".
Also, main problem w DDD (or any architectural approach) is that you have to make biggest architectural decisions when you basically have the least amount of knowledge about the system/problem.
- pydry 4y ago>I don't get how using ubiquitous language can slow down the projects. It doesnt. Ubiquitous language is more or less just a reworking of system metaphor from XP and was a fine idea even then but DDD took the idea, barely tweaked it and layered a bunch of quite horrible design patterns around it. Ubiquitous language and bounded contexts are the best parts of DDD by far but theyre also the least original and the least well developed concepts and honestly DDD doesnt have much of anything interesting to say about either one of them beyond what they are and that theyre important.
- c048 4y agoI wish I could upvote you more than once. You hit the nail on the head, thank you.