Weeks of coding can save you hours of planning
summary
Claim: weeks of coding can save you hours of planning flips: spending focused discovery saves months of wasted rework. Uses event storming, whiteboard prototyping and architecture katas to force early domain questions, surface hidden requirements, and map domain boundaries. Advocates INVEST user stories, acceptance criteria, C4-style zoomed diagrams, and timeboxed spikes with a “plan to throw away” mentality. Teams that adopt these practices report far fewer long refactors and clearer business tradeoffs when building APIs and multilingual commerce features.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:00The problem of lost information
- 5:14Understanding the problem
- 8:01Focusing on implementation
- 10:41Agile manifesto and principles
- 13:56INVEST in user stories
- 17:35Event storming and DDD
- 20:39Architecture katas
- 25:44Training the gut feeling
- 32:53Strategic planning steps
- 35:55Refining the planning process
- 39:03Q&A and closing
related talks
51mGetting Real Value out of your Planning Efforts with Story Mapping
27mBuilding Applications Better the First Time
38mFrom Conversation to Software
50mHow EventStorming Transformed Our Domain Modeling Process
31mHow we increase execution by 10x at Coda
45mBeyond Estimates
19mProcesses & Tools over Individuals & Interactions
58mTechnical Practices that Take Time but Save Time