IntroDDDuction
summary
Argues that tactical DDD (entities, value objects, repositories) is easy to learn but the payoff is in strategic DDD: ubiquitous language and bounded contexts, illustrated by a four‑year project where price formulas differ between purchase orders and sales orders. Mentions PHP background, the 2004 Evans book, six‑seven pet projects and a two–three month pause while grappling with bounded contexts, then applies DDD to a large legacy app to improve communication and models — it produces concrete design changes.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:48Legacy Applications
- 3:29Why Do We Still Write Shitty Software
- 6:30Programming Is All about Communication
- 8:26Tactical Domain Driven Design
- 10:47Strategic Domain Driven Design
- 15:36What Is Domain-Driven Design
- 26:56The Ubiquitous Language
- 35:59What Does Domain-Driven Design and Communication Have in Common
related talks
01h 05mGetting to DDD: Pragmatic or Principled?
01h 11mAn introduction to DDD
45mLearning to Love DDD - a Tale of Two Products
58mDDD really matters!
27mConfessions of a Backend Developer
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
49mDomain-specific languages with PHP
50mA live dialogue "DDD: You're doing it wrong"