DDD Really Matters!

on YouTube ↗01h 02m

" summary

Five concrete proposals: start with purpose (use the Monty Python/editor example and a military micro‑services analogy to justify purpose before tech), treat the domain as context and focus on the core domain, create a shared ubiquitous language or small DSLs so domain experts can co‑program, protect experiments with a circle of safety (small teams, boundaries, a museum of failure), and attack the global bottleneck first while automating repetitive work (continuous delivery correlates with profit).

AI-written summary · about

" chapters (18)

1. 0:00Introduction
2. 1:47Presentation
3. 6:31Problems
4. 7:58Holy Grail
5. 11:30Purpose
6. 17:42Sound Blocker
7. 24:46Managers vs Developers
8. 29:22Dependency Diagrams
9. 38:34Law of Nature
10. 41:09Language
11. 43:44Immune System
12. 46:54Communication Style
13. 48:54Failure
14. 51:09Circle of Safety
15. 52:49Bridge
16. 54:17People Automation
17. 56:04The bottleneck
18. 58:58Traps

" related talks

• 58mDDD really matters!Jimmy Nilsson · NDC Sydney 2019
• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 37mBuilt to last: A domain-driven approach to beautiful systemsAndrew Hao · RailsConf 2017
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 44mDependencies; Devil or Darling?Jimmy Nilson · Craft Conference 2023
• 57mDomain-Driven Design in ProductlandAlberto Brandolini · FlowCon France 2024
• 50mDomain Prototyping or Design Is How It WorksTobias Goeschel · KanDDDinsky 2019
• 01h 05mGetting to DDD: Pragmatic or Principled?Julie Lerman · NDC Oslo 2019