Culture - The Ultimate Context
summary
Argues that culture is the ultimate context for language and therefore for software modeling, making two concrete claims: collaboration requires shared language and shared intent, and DDD succeeds when a shared domain model is actually used. Cites Tomasello-style evidence (chimps never carry logs together, infants show early turn-taking) and the physical cap on coordination — Amish barn limits ~100–150 people — to explain why software scales differently (compute follows Moore’s law, time does not). Gives practical rules: listen to domain stories, adopt existing terms, and avoid changing accepted terminology. pointing and demonstratives as coordination
AI-written summary · about
chapters (19)
- 0:00Introduction to collaboration
- 1:56Lessons from Amish barn raising
- 3:42Limits of physical constraints
- 5:29Evolution of language and intent
- 7:44Human vs primate cooperation
- 9:38Recursive mind reading and culture
- 12:45Language as a platform
- 15:04Defining words and meaning
- 19:34World models and coordination
- 21:58The aesthetic value of doing together
- 25:00Shared abstractions and metaphors
- 28:09Context and demonstratives
- 30:34The role of pointing in communication
- 34:06Culture as the ultimate context
- 37:28Stories and cultural transmission
- 41:08Applying DDD to shared models
- 44:36DDD universals and cultural ideas
- 47:30Balancing diversity and uniformity
- 49:00Practical applications for DDD
related talks
01mSoftware doesn't tolerate ambiguity
16mDDD is not enough: the future of software development -
40mLanguage Games
44mStrategic Domain-Driven Design for dummies
48mObject modeling: Theory vs Practice. Round 1
53mSoftware Design: Beyond Boxes & Lines
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
49mCultures of Programming