The Ubiquitous Language
Download as PPTX, PDF2 likes2,332 views
The document discusses the importance of having a shared or "ubiquitous" language within development projects to facilitate effective communication and prevent failures. It states that an ubiquitous language provides common ground for learning and communication, with the domain model acting as the backbone of this shared language. While cultivating an ubiquitous language is challenging, it is worthwhile as communication and learning are very important.
The Ubiquitous Language
- 2. The Ubiquitous Language domaindriven.be – DDD basics
- 4. Talking different languages makes projects fail.
- 6. When a customer moves, I want to send him an email.
- 7. I’ll use a micro ORM to update the database. I think I read something about a fluent SMTP library too...
- 12. Users don’t use your software to modify records in a database.
- 15. Translations are error prone. Things go lost in translation.
- 16. Projects don’t need translations, they need a shared language.
- 17. The ubiquitous language is much needed common ground that enables learning and communication.
- 21. The model is the backbone of our shared language.
- 22. Code can’t lie, documents can.
- 23. Well-written code can capture the language as good as any document
- 25. Documents have a supporting function.
- 26. Keep a focused set of documents and be agressive about keeping them consistent.
- 28. Visualizations are awesome, but they are volatile, used to communicate ideas. Trying to keep them updated will constrain you.
- 29. Easier said than done...
- 31. “A DDD'er walks into a bar.... no, a pub ... no, a bistro... “ - @ToJans
- 36. Cultivating an ubiquitous language is not trivial.
- 37. But might be worth it... Communication and learning is just so damn important.