Factory, Workshop, Stage
summary
Argues the 60‑year factory metaphor is misleading and offers a concrete replacement: a stage model that treats development as a live, deadline‑driven creative process. Uses consulting case studies, a Google study showing psychological safety and equal talk, a cited 68% project failure stat, and historical analogy (miasma vs germ theory) to show problems like caching choices and naming are people problems. Claims applying the stage model reveals who must renegotiate roles, why scaling fails, and how teams actually ship useful work.
AI-written summary · about
chapters (7)
- 0:00Start
- 18:14Cache invalidation
- 20:44Naming things
- 24:57Build a "product"
- 29:06Miasma
- 37:381. A Script
- 41:57Performance
related talks
48mTechnical Modeling as a Practice
26mFeatures Versus Futures
50mBut First, the Team!
28mJourney from Design Afterthought to Design First
46mPanel Discussion: The Agentic Software Factory That Enterprises Actually Need
43mChange Your Focus
01mSoftware doesn't tolerate ambiguity
01h 08mThe Creative Process for Game 'Factories'