Domain-Driven Design in Productland

on YouTube ↗57m

" summary

Argues that applying Domain-Driven Design to product teams requires concrete practice: use event-driven models to get trustworthy experiment data instead of brittle BI on legacy databases (example: detecting transfers via cancellation+rebook scripts created accidental complexity); prefer pairing across disciplines and short deploy cycles (some teams deploy experiments in a day, others wait two weeks) to cut handoffs; keep separate surface and implementation languages; prioritize design integrity so models stay ready to evolve and experiments stay cheap and clear.

AI-written summary · about

" chapters (12)

1. 0:00Welcome and introduction
2. 1:51DDD in product development
3. 5:00Mindset and learning challenges
4. 12:13Cross-discipline collaboration
5. 20:41Product strategy vs DDD determinism
6. 28:10Flow and experimentation friction
7. 31:22Language differences in DDD
8. 37:43User-facing vs implementation language
9. 42:01Customer count and product space
10. 46:00Design integrity over technical debt
11. 51:20Predicting future needs
12. 55:36Closing insights and Q&A

" related talks

• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 58mDDD really matters!Jimmy Nilsson · NDC Sydney 2019
• 54mDomain-Driven Design and Team Topologies for Product-led OrganizationsNick Tune · NDC Porto 2022
• 45mLearning to Love DDD - a Tale of Two ProductsChris Simon · NDC Oslo 2022
• 50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDDH. Schwentner · code.talks 2017
• 38mDomain-Driven Design & Team Topologies Hands-onNick Tune, Zsófia Herendi · Craft Conference 2022
• 01h 11mAn introduction to DDDRob Allen · PHP UK Conference 2024