Earlier quoted context omitted.
Borderline thread necro here but... > "Have you considered that our long lead times on inventory means we increase our holding costs?" What's frustrating about this is now we also have to understand the business overall, and that's kind of the problem in the first place: nobody has the patience to explain it. So in addition to coming up to speed on whatever tech stack they have, we're going to have to find someone wh…
I didn't wait for anyone to explain it to me, I went to the library and checked out a bunch of books they had on Supply Chain Management/Operations Management and Inventory Control and then read them. That gave me enough of a grasp of the principles and more importantly the nomenclature that I could then talk to people in their language not mine. To me it's a normalised series of tables to them it's WIP inventory. On…
> Unfortunately in my experience (couple of decades) most business people don't want a common language, they want you to understand theirs.
The “common language” of DDD was the language of the business domain, so that’s in line with DDD.
The practical problem is that the language of many business domains is often highly context dependent, making it unsuitable for direct use where ambiguity must be avoided even without context, and trying to namespace things to map to the specific relevant business contexts is often impractical.