Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 7: Teaching Through Speaking #

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, dry mouth at the lectern, a moment ninety seconds in where the room goes silent and the speaker realizes nobody is reacting to anything yet. This is a stress response, not a personality flaw, and the only treatment is reps. The fifth talk is dramatically less terrifying than the first. The twentieth is something close to enjoyable.

And here is the unhelpful but honest thing about getting to the twentieth: there is no shortcut. The books help around the edges — Resonate is good, Patrick Winston's "How to Speak" is excellent, watching Sandi Metz teaches you what good looks like — but none of them get you to the twentieth talk. Only twenty talks do. The implication is that you should submit to a meetup roughly now, before you feel ready, because feeling-ready never arrives in advance. It only arrives retrospectively.

Most engineering talks are bad in the same five ways: too much content for the time, slides that compete with the speaker, a demo that wasn't tested on conference WiFi, a flat opening that takes ninety seconds to declare what the talk is about, and a Q&A where the speaker either argues with the questioner or thanks them effusively for an unrelated comment. The fix for each is mechanical. Cut your content in half before you rehearse. Fewer slides, larger fonts, never read from the slide. Record the demo as a fallback and pre-record any network call. Write your first sentence to be concrete, specific, and arresting. And learn the phrase "Thanks — let me think about that; can we discuss after, since I want to do it justice?" for the hostile, off-topic, or rambling question. Avoiding these five puts you in the top 20% of engineering speakers before any artistry is involved.

The single biggest improvement most talks could undergo is being shorter inside the same slot. A thirty-minute talk can carry maybe six minutes of genuinely new information that the audience will retain; the other twenty-four minutes are setup, examples, demonstration, breathing room, and the pauses the audience needs to absorb anything at all. Engineers, who write dense documentation for a living, default to filling all thirty minutes with new information, and the result is that the audience retains none of it. Cut your content. Then cut it again. This is the same discipline the writing module taught, applied at a different scale — except the listener, unlike the reader, cannot scroll back.

On slide aesthetics, do not pick a religion: the no-slides philosophical talk, the beautiful-minimal-deck talk, and the dense code-on-screen talk are each right for some talks and wrong for others. A talk about engineering ethics works with no slides; a talk teaching a specific framework technique probably needs code on screen. Pick per talk; don't fight the topic.

One more thing, about the "introvert engineer" identity, which is real and misused. Introversion is about energy recovery, not capability. Some of the most effective engineering speakers are clear introverts who deliver the talk and recover quietly afterward. Speaking does not require being an extrovert; it requires thinking clearly under low-grade physical stress for thirty minutes, which is a buildable skill. "I'm an introvert" is sometimes accurate self-knowledge and sometimes a story that protects you from the practice. Notice which one it is in your mouth. It is worth the noticing, because a recorded conference talk is one of the densest credibility artifacts an engineer can produce — it reads as evidence of senior-level thinking to people who will never read your code — and skipping the medium entirely should be a decision, not an avoidance.

Conclusion #

The terror is normal and the fix is reps. Submit before you feel ready. Cut your content in half, then again. Don't adopt a slide religion. Plan the demo failure like any other partial outage: detected fast, degraded gracefully, narrated honestly. Speaking is a learnable skill that introverts can do, and the recording at the end is a career artifact that keeps working for years after the room empties.

Predictions #

  • Your first talk will feel awful in the moment and look noticeably better than you remember when you watch the recording. Engineers consistently misjudge their first talks in the negative direction.
  • You will rehearse at least one talk too few times. The number of out-loud rehearsals nobody regrets is five; most engineers do two or three and discover the difference on stage.
  • You will have one demo fail within your first three talks. How you handle the failure will be more memorable to the audience than the demo would have been if it worked. Have the fallback ready.
  • The Q&A will be easier than the talk — answering is a lighter cognitive task than producing. You will be surprised by this exactly once.
  • You will get one obnoxious questioner in your first ten talks. The audience will be on your side; do not escalate.
  • You will start to enjoy speaking somewhere around talk four or five. Before that, expect not to. The unbroken practice through the unenjoyable phase is the entire mechanism.