Deliver a 30-minute conference-grade talk: slides that work (or the deliberate absence of slides), a demo that survives failure, and a Q&A you can hold. A talk is a real-time system: the audience is the framebuffer, questions are interrupt handlers, the demo is a network call you can't retry, and you are the runtime. Most engineers fail at talks by treating them as blog posts read aloud — a batch job in an environment that demands streaming. Budget time per section like a latency budget, design for the room being colder than expected, and plan the demo failure like any other partial outage: detected fast, degraded gracefully, narrated honestly.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The terror is real and I am not going to talk you out of it. Engineers giving their first conference talk routinely have the same physical experience: insomnia the night before, d…
A talk is a different cognitive product from a post. The reader controls a post's pacing; the listener controls nothing — they can't scroll back, and every minute that doesn't ear…
Approach: Essential
Approach: Essential
Approach: Important
1. Submit a talk proposal to a meetup within 30 days. Don't wait until you "have something to say." Submit, then write — the deadline is the writing tool. 2. Deliver a 15-minute t…
6 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.