17. Community Presentation

Chapter 17 of 18 · 20 min

KEY INSIGHT

A conference talk is not a paper read aloud. The best talks show what papers cannot—enthusiasm, intuition, and the human story of discovery. Presenting to an audience requires different skills than writing for readers. People cannot re-read a confusing sentence; they can only ask confused questions or zone out. ### Talk Structure **Hook (30 seconds):** Why should the audience care? Start with a problem, demo, or provocative question—not with "I'm going to talk about X." **Context (2-3 minutes):** What did people do before your work? What are the limitations? This establishes why your work matters. **Approach (5-8 minutes):** What did you build? Show architecture, key innovations, design decisions. Use visuals, not bullet points. **Results (3-5 minutes):** What did it achieve? Show numbers, comparisons, demos. Let the data speak. **Implications (2-3 minutes):** What does this mean for the field? What can others learn or build on? **Q&A preparation (implicit):** Anticipate questions and prepare answers. ### Visual Design for Talks Slides should support the spoken content, not repeat it: ```python # BAD: Bullet points that repeat what's said """ - Our system uses a novel retrieval mechanism - It achieves 94% accuracy - It's 2x faster than the baseline """ # GOOD: Visual that the speaker elaborates on """ [Architecture diagram] "The key innovation is the indexing layer here— instead of brute-force search, we use..." """ ``` Use high-contrast colors, large fonts (minimum 24pt for body text), and minimal text. One idea per slide, maximum. ### Handling Nerves Presentation anxiety is universal. Mitigation strategies: - **Practice until boring**: Know the material so deeply that nerves don't affect delivery - **Video record yourself**: Identify nervous habits (filler words, pacing) that you don't notice in the moment - **Arrive early**: Familiarity with the room reduces anxiety - **Breathe**: Slow, deliberate breathing before starting resets the nervous system ### Live Demos Demos are high-risk, high-reward. A working demo creates memorable impact. A broken demo creates memorable failure. ```python # Demo safety checklist DEMO_CHECKLIST = """ [ ] Demo runs correctly in the presentation environment [ ] Backup recording exists if live demo fails [ ] Demo data is appropriate for presentation context [ ] All necessary resources are accessible offline [ ] Timer set to know when to advance without counting """ ```

EXERCISE

Prepare a 10-minute presentation of your research system. Record yourself presenting it. Identify: (1) one moment where you lost the thread, (2) one slide that was confusing, (3) one technical claim that wasn't supported. Iterate until the recording flows smoothly.