DDD really matters!
summary
Argues that Domain‑Driven Design wins when teams start with purpose first and treat the business as the primary context, reorganize into cross‑functional outcome teams, and fix the real bottlenecks instead of piling on tools or headcount. Recommends evolving a ubiquitous language (even as internal DSLs / language‑oriented programming) so domain experts can read and change behavior, uses a simple code‑size cost heuristic to convince managers, and insists on a circle of safety around new initiatives so experiments can iterate to success.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 8:05How can we create great together
- 8:41Holy Grail
- 11:57What to start with
- 12:31The purpose
- 16:27Context
- 18:30Setting out
- 19:21Soccer example
- 19:53Defensive vs offensive
- 21:22Organizations
- 23:38Alternative
- 25:43Code vs Money
- 28:24Size matters
- 29:17More code
- 38:48Software is magic
- 39:43Software curve
- 42:18Language oriented programming
- 43:10Circle of safety
- 43:30The immune system
- 45:03Our worst enemies
- 48:58Making mistakes
- 50:28Shank Cloud Computing
- 51:33What will we use it for
- 52:37Whos the fastest
- 53:50Working with the bottlenecks
- 56:30Solving the bottlenecks
- 56:48What really matters
- 57:13What happened now
- 57:33Dream
related talks
01h 02mDDD Really Matters!
38mDomain-Driven Design: Hidden Lessons from the Big Blue Book
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
57mDomain-Driven Design in Productland
01h 11mAn introduction to DDD
29m20 Years of Domain-Driven Design: What I’ve Learned About DDD
01h 05mGetting to DDD: Pragmatic or Principled?