When the demo has to land
summary
Shows exactly what gets built and what actually worked: live demos for Microsoft and GitHub keynotes, a 100‑minute analyst demo distilled from 19 densely packed pages of demo script, eight minutes to cover a dozen features, and examples of using video backup / cooking show technique and multiple desktops to avoid failure. Covers honest rules for AI nondeterminism, when to skip a feature, the ethics of kayfabe, and how much engineering time (weeks or ~100 hours) goes into a reliable demo.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 10:14Structuring a demo narrative
- 12:22Knowing audience and product
- 14:30Handling unreliable software
- 20:58Balancing integrity and expectations
- 26:21Prioritizing demo reliability
- 30:59Q&A
