Hacker News Reader

Comment by eggsby | Hacker News Reader

Seems to be enforcing ‘ubiquitous language’ at the machine level - not some kind of mathematical dual where one is invertible to the other - but enforcing soft skills as hard skills.

  ‘protobuf specs dont have enough information for us to codegen iceberg tables so we will write a new codegen spec language’

what makes a duck a duck? when we know which tables we can find it in

View on HN

Except that "Ubiquitous Language" is supposed to refer to terminology within a specific Bounded Context. In DDD it is desirable and expected that there is a mapping between them. This proposal tries to entirely erase Bounded Contexts. This is what I mean about people not understanding the words.

So in the sense of "what do we do about terminology not matching across an organisation" this and DDD are literal opposite solutions: one says "erase differences with a central definition (and bear the coordination costs)" while the other says "encourage differences with local definitions (and bear the mapping costs)".

UDA enables both approaches. each has its place.

It may enable both approaches, but the article positions only one. I mean, the title is "Model Once, Represent Everywhere".

Reply on news.ycombinator.com