the ubiquitous language
DESCRIPTION
Looking at the strategic side of Domain Driven Design, this slide deck goes into where it all starts; the Ubiquitous Language.TRANSCRIPT
@JefClaes - jefclaes.be
The Ubiquitous Language
domaindriven.be – DDD basics
Talking different languages makes projects fail.
When a customer moves, I want to send him an email.
I’ll use a micro ORM to update the database. I think I read something about a fluent SMTP library too...
Users don’t use your software to modify records in a database.
Translations are error prone.Things go lost in translation.
Projects don’t need translations, they need a shared language.
The ubiquitous language is much needed common ground that
enables learning and communication.
The model is the backbone of our shared language.
Code can’t lie, documents can.
Well-written code can capture the language as good as any document
Documents have a supporting function.
Keep a focused set of documents and be agressive about keeping them consistent.
Visualizations are awesome, but they are volatile, used to communicate ideas. Trying to
keep them updated will constrain you.
Easier said than done...
“A DDD'er walks into a bar.... no, a pub ... no, a bistro... “
- @ToJans
Cultivating an ubiquitous language is not trivial.
But might be worth it...Communication and learning is
just so damn important.
Thank you! @JefClaes