DDD is not enough: the future of software development -
summary
Software engineering since 1968 creates a widening chasm between code and real-world domains, and DDD alone is insufficient; the proposal is to gather domain stories—about 95% learned from stories—and assemble them into thick description ethnographies, then produce a simple gestalt map (bubble-and-arc elements and relationships) and identify bounded contexts and evocative triggers (sensory cues that recall complex behavior). Teams combine these artifacts to map domain patterns to software, reducing miscommunication and producing systems that actually match practice.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:18Domain in the world
- 5:48Objectoriented
- 6:30User Stories
- 7:33DDD
- 8:34Software Engineering
- 9:45Ethnography
- 10:42Description
- 10:58gestalt map
- 11:48evocative triggers
- 12:55domain experts
- 14:39patterns
related talks
29m20 Years of Domain-Driven Design: What I’ve Learned About DDD
45mDon't Overdose on Domain-Driven Design
44mStrategic Domain-Driven Design for dummies
01h 00mFrom Domain Driven Design DDD to Delivery
35mTrivialization of DDD or Not?
01mSoftware doesn't tolerate ambiguity
38mWhat I talk about when I talk about Domain Driven design
55mHigh-speed DDD