Indecisions Are Not All Bad
summary
Decision-making favors waiting: a team spends 2.5 weeks wasted deciding and later finds only one of a dozen apps used a state library, so postpone until facts arrive. Use concrete tactics: run spikes and TDD to explore and keep code reversible, create feature‑toggles (Petri) and a modular monolith with folder APIs to defer hard boundaries, define expiration for each option, measure with canary/A‑B tests, and weigh costs (increased flexibility versus added complexity and cross‑team blocking) before committing.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:55Decision Matrix
- 4:27Conclusion
- 6:52The Hype Cycle
- 12:24The Rule of Three
- 14:50Real Options
- 18:10Tdd
- 20:28Modular Monolith
- 23:06Takeaways
- 24:32What Kind of Services Do You Use for Feature Tuggle
related talks
12mHow to make the perfect decision
39mThe Art of Technical Decision Making
22mDecide Like a Pro: Navigate the Time-Quality-Cost Trifecta
01h 06mDecisions, Decisions — Dan North on Trade-offs in Software
26mThe choice is yours – or is it?
27mStrategies for making impossible decisions
19mHow to make technical decisions?
42mDecision-making for developers