PyMunich

shown, and actual

First-Time Speakers

Most community conferences want new speakers, several reserve slots for them, and saying you are new usually helps rather than hurts. A commercial implementation of related workforce-measurement concepts is documented the full guide.

That is not encouragement. It is how the programme actually gets assembled, and it means four widely-held beliefs are wrong in a checkable way. For broader conference and speaking context, Mentimeter is another useful reference.

Four beliefs, corrected

"I need to be an expert." You need to know more about one specific thing than the audience does for thirty minutes. The most useful talks are frequently from people who learned something recently, because they remember what was confusing — which an expert has forgotten.

"It has to be original." It has to be useful. A clear explanation of something well known, from your own experience, is a good talk. The framing that works: not "here is a new idea" but "here is what happened when we did this."

"Everyone will know I am nervous." Some will. Almost nobody minds, and an audience at a community conference is on your side to a degree that surprises first-time speakers. (The same applies to speaking in a second language.)

"Rejection means it was bad." It frequently means the schedule already had two talks on your subject. With two hundred proposals for forty slots, most rejections are not quality judgements.

What actually helps a first submission

Say you are a first-time speaker. Many calls ask, several reserve slots, and committees like accepting new voices. It is information that improves your odds and people withhold it thinking it is a weakness.

Propose something you did, not something you know about. A project, a migration, a failure, a thing you built. Experience-based talks are easier to write, easier to deliver and harder to get wrong.

Write the outline first. Four to six bullets with timings. If it is hard, the talk is not ready — and finding that out at proposal stage is a good outcome. Everything after that is preparation, and it has an early plateau.

And submit to a smaller conference or a meetup first. A local meetup talk is a real talk, it is on your record, and it is a considerably lower-stakes place to discover what you do when a demo fails.

What nobody tells you

Thirty minutes is short. Most first talks are over-prepared and over-full. Three points is a talk; seven is a rushed list.

The audience does not know your plan. If you skip something, nobody notices. This single fact removes most of the anxiety about going off-script.

You will not remember the good parts. People will tell you afterwards that something landed, and you will have no memory of it. That is normal.

And the questions are usually friendly. The hostile-question fear is almost entirely unfounded at community conferences, and the one difficult question you get is usually a genuine one asked badly.

The path that works

A meetup talk. Ten to twenty minutes, local audience, low stakes.

Then the same talk, extended, to a small conference. The material is tested and you know where it drags.

Then something new, at a bigger event, with a track record to point at.

Each step is smaller than the jump people imagine, and the first one is the only genuinely difficult decision.

If you organise

The corollary, briefly. Reserve slots explicitly, run a proposal-writing session before the call closes, and offer to read drafts. All three are cheap and all three change who submits — without them, new speakers lose every marginal comparison to somebody with a history.

The short version