I'm just at #ManuSec (a #Cybersecurity conference focused on manufacturing/ #OtSecurity )
A lot of discussion focuses on finding a common language between IT and OT.
This reminds me so much of the #UbiquitousLanguage of #DomainDrivenDesign (#DDD)
I expect that we will discover that this only works in a #BoundedContext (sadly I fear we will need 5-10 years for that 
)
#Newspeak IS our #UbiquitousLanguage for #DDD of Society in 2025. Almost!
Next time when #Orwell and #Huxley come up in #discourse remember:
We live in #dystopia NOW!
Unseen by our #DistractionEconomy blindfolds.
We're the frogs for years, taking a nice warm bath to unsee #RootCause of #ClimateChange temperature rise:
Vice has free reign as #truth is destroyed.
We MUST be #Plainspeaking
We MUST use #CommonSense
We MUST restore #Reality
I think #UbiquitousLanguage is still one of the most underrated concepts from #DDDesign.
Especially in tests.
Zbieram materiały na mailing o Ubiquitous Language jakiego prawdopodobnie nie znacie.
Jak myślisz, co w nim się znajdzie?
Daj znać w komentarzu. 
Alert 
: Manage Team Cognitive Load - an example from the field!
I supported a team with their designs a while ago, embracing #DomainDrivenDesign. As part of the journey, they built a strong relationship with their business counterparts and nailed the concept of #UbiquitousLanguage. As a consequence, even the purpose of the team evolved, which means that artifacts needed to be updated.
Small 
1/
For the new Code Craft Academy assessments, I took the decision to provide a skeleton domain model (as data classes) for participants to hang new behaviour on. My thinking was that it would constrain their interpretations of requirements, and in that respect it certainly did. Most interpreted "add item to order" and "receive stock in the warehouse" the same way.
Took me back to the old days when we used to think about and talk about the design a bit before we wrote code 
Some time ago I was the new kid in a meeting with various teams who were about to conclude their talks, having agreed on integrating using an existing product identifier.
To verify, I asked what exactly that was for everyone:
- product_uid
- base_sku
- variant_sku
- ean
- name
These were not the same. Turns out folks had implicitly made the translation to their own domain language.
Don't assume you're talking about the same thing just because it has a similar name.
Exciting news for JetBrains users interested in #contextive - the latest plugin platform EAP (early access program) RC includes support for the hover function!
Contextive should be ready to launch in the Jetbrains plugin marketplace when this RC goes GA.
#domaindrivendesign #ubiquitouslanguage #jetbrains #intellij @nick_tune @yellowbrickc @__maxs__
I really encourage teams to have their own vocabulary:ubiquitous language.
But when you need to talk with different teams together yiu can confuse word because for a team the "xyz" term means a thing and for another one it means a different thing. How do you deal with that?
#ddd #domaindrivendesign #UbiquitousLanguage
For non English speaking coders...
Especially if working in #DDD
#UbiquitousLanguage requires common language & terminology in code and business
Yet, I see many benefits of coding in English....
- code homogeneity between public front end and internal code
- easier to find subcontractors
- English kinda is _the_ standard
- devs are more used to it
- pear review
- "auditability" (For context, my company's lg is FR... but HQ is British)
- ...
What do you do ?
(Boosts appreciated)
@itwasmattgregg Naming is from a perspective - something "sent" to an API is "received" in your application - think of who can see the names.
Use #ddd to discover terminology important to your domain experts and use it in naming throughout the solution. #UbiquitousLanguage
SomeWaysOf Writing_hurt_and others-less-so. Consistency and conventions also communicate meta aspects such as type or purpose.
Post back with how it goes! Such a critically important subject!
@kjoo Yes, but
:)
In large organizations #UbiquitousLanguage is a myth, an idea, a goal that you will never reach. And business analysts’ job is to TRANSLATE #UbiquitousLanguage of one department to #UbiquitousLanguage of another one.
You are an interpreter that assures everyone understands one another and cooperate to implement a change that is needed in the organization.
‘Cause every part of big organization has it’s own #UbiquitousLanguage that suits it’s own special needs best.
In #businessanalysis finding the right wording is important. And even in the #informationtechnology naming is one of the two hard things (besides cache invalidation and the off-by-one error 
; see https://lnkd.in/d9gwCmJq). #DDD as a technique is stating the importance of an #UbiquitousLanguage.
But still, finding a correct name is hard. And we shouldn't think that the name changes the behavior of thing.
Als ze in de lagere school het onderwerp, de persoonsvorm en het gezegde eens op die manier zouden benoemen, dan zou het wel handiger zijn om de kinderen te helpen met #zinsontleding. #ubiquitousLanguage
Where #developers get #UbiquitousLanguage wrong in #DDD is that they misapply data normalization techniques to similarly named concepts existing in different #BoundedContexts.
In every subdomain, you may call a Customer a Customer.
A Customer may need an email address in the Customer Support subdomain. It doesn't need an email address in the User Review subdomain, or in the Billing subdomain, or in the Order Processing subdomain.
Don't overnormalize similar concept occurrences into one entity
in calmness 
