How to Cultivate a Language
summary
Argues teams must cultivate a shared domain language using semiotics and literary theory rather than just a glossary, recommending active work on dictionary vs encyclopedia knowledge, building semantic and encyclopedic competence by negotiating with real users, and testing designs with the adversative "but" to expose required constraints. Gives concrete examples — supermarket misassumptions, scientist vs native butterfly, and RabbitMQ performance ranges of ~20–25k messages/sec — and separates essential vs typical properties for types.
AI-written summary · about
chapters (14)
- 0:00Introduction to language in DDD
- 1:13The semiotics of signs
- 3:15Metaphors and explanatory power
- 5:59Philosophy of interpretation
- 10:32Possible worlds and reader models
- 14:12Bridging knowledge gaps
- 18:44Inferential vs. referential
- 21:58Dictionary vs. encyclopedia
- 25:54Distortions and approximations
- 29:09Abduction in communication
- 32:44Cultural stabilization
- 36:48Practical domain language tips
- 42:16Essential vs. typical properties
- 47:25Cultivating software cultures
related talks
30mHow you write matters in open source
55mGardeners, Artisans or Engineers... but Not Minstrels
27mProduction Language Specification - Requirements for Multiple Usages
44mLiterary Theory looks at Readable Code
47mGlobalise the docs
39mDeveloper’s Torment: The Documentation
28mNavigating Corporate Language: Developing a Graph-Based Glossary
29mHumanizing Your Documentation