Eating an Elephant: Conquering big projects one bite at a time.
summary
Starts with clarifying ubiquitous language and the core bounded context so requirements shrink to what actually matters, not a sprawling spec. Uses domain-driven design to separate problem and solution space, proves models with outside-in TDD and a pragmatic dumb smart approach (mocked returns first), and prioritises a platform-based MVP: CI/CD, auth, logging, deploy tests and integrations early so microservices and event patterns can be validated before scaling. Claims this sequence prevents wasted features and long rework.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:05Who am I
- 3:44Why
- 10:24The Dunning Kruger Effect
- 14:18Ubiquitous Language
- 19:27Ubiquitous Dictionary
- 22:01Domain Model
- 26:54TDD Approach
- 33:00The MVP
- 38:27Platformbased MVP
- 40:47What a platformbased MVP looks like
- 44:57Recap
related talks
43mSweat the Small Stuff
46mAchieving an evolutionary architecture through simplicity
51mDon’t Feed the Pigeons Some Principles from Real World Internal Developer Platform
25mThinking Architecturally
29mDriving clarity in ambiguous projects
57mDelivering Unicorns
38mSolving the Hard Problems
58mRefactoring the Architect’s role