Greater Quality Through Tactical Domain-Driven Design

on YouTube ↗54m

" summary

Claims that untargeted logic causes most waste—60–80% of code is business logic—and cites CISQ estimates of ~$2.08T (2020) to $2.4T (2021) in software-related cost. Recommends mapping domains with event storming and the bounded contexts canvas, organizing teams by capabilities (2–7 people), modelling behavior as aggregates (examples: process bill payment with 2–3 commands) and using messaging/outbox patterns to decouple modules; shows these steps shrink change time and reduce maintenance waste.

AI-written summary · about

" chapters (14)

1. 0:00Introduction
2. 3:11Future of software design and DDD
3. 7:48Poor software quality costs
4. 11:02Systems thinking and DDD basics
5. 13:51Software logic design gap
6. 17:49Canonical models to bounded contexts
7. 23:23Distributed systems and DDD patterns
8. 27:39Event storming and wireframing
9. 30:28Aggregates, factories, repositories
10. 35:04Design quality and profitability
11. 37:52Q&A
12. 43:45Q&A
13. 47:02Q&A
14. 50:19Q&A

" related talks

• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 58mDDD really matters!Jimmy Nilsson · NDC Sydney 2019
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 44mDependencies; Devil or Darling?Jimmy Nilson · Craft Conference 2023
• 37mBuilt to last: A domain-driven approach to beautiful systemsAndrew Hao · RailsConf 2017
• 40mFrom Domain Boundaries to Software ArchitectureNick Tune, Maxime Sanglan-Charlier · Copenhagen Developers Festival 2023
• 01h 26mChaos Development: Removing Software as the Inhibitor of AgileFred George · Craft Conference 2019
• 34mPractical Tools and Strategies for Tackling Legacy PracticesAlejandro Scandroli · CAS 2018