Home / Guides / Lightning Talks

Lightning Talks

A lightning talk is a short, focused talk that engineers give at conferences and meetups all the time. They are everywhere in the Python and AI communities, which is the world this course lives in, so getting up to do one is good practice for a thing that comes up a lot once you are working.

In our class it is a low-pressure way to share one useful thing with your classmates. You do not need to be an expert. You only need to be one step ahead of the room on one small thing.

You give two of these during the semester, one in each half, worth 3 participation points each. They are on a rolling sign-up, so you claim a slot when you are ready.

⏱️ What a Lightning Talk Is Here

  • Two minutes, one idea. It does one thing well. Leave the tutorial and the deep dive for another day.
  • Then two minutes you run yourself. See the next section. This half is the part most people underestimate.
  • Given live, at the start of class. You present from your screen or a couple of slides.
  • Slides are optional, and HTML beats PowerPoint. If you want visuals, throw together a simple web page or run a live demo. Keep it to three screens at most.
  • The instructor has your back. If something falls through, the instructor covers the topic. This is a safe place to practice in front of a friendly room.
  • Full credit for a real talk. You are graded on showing up with something real and running the discussion, never on polish.

🗣️ The Second Two Minutes Are Yours to Run

Your talk is four minutes total: two of you talking, then two of discussion that you lead.

Close the talk on a question your classmates can genuinely disagree about, put it to the room, and call on people yourself. The instructor stays out of it. A talk that ends with the room silent has not finished.

This is easier than it sounds if you plan the question while you build the talk instead of improvising it at the end. Two things make a question work:

  • It has more than one defensible answer. "Should you let an agent write the whole first draft?" beats "Is testing important?"
  • Everyone in the room can answer it. Anchor it to something they have all done. "Has anyone had an agent add a library you did not ask for? What did you do about it?"

If nobody speaks up in the first few seconds, call on someone by name. That is allowed, it is expected, and it is the fastest way to break the silence.

🌐 Your Second Talk Runs from Your Own Page

The first talk can be anything: your screen, a slide, a live demo.

For the second talk, in the back half of the semester, present from a web page you built and deployed at your own URL. Any shape you like, and it can be as simple as one page with your three points on it. By that point in the semester an agent will get you there in minutes, which is exactly why it is the requirement. Send the URL along with your topic when you lock it in.

💡 What to Talk About

Pick one thing you found interesting this week. It does not have to be something you built. It can be something you learned, or a technique you think others will want. Four kinds of topics fit well:

  • AI. A prompt that worked, a tool you tried, a workflow, or an AI bug you caught. "The one line I add to every prompt to get cleaner code."
  • Web. An HTML, CSS, JavaScript, or deployment trick or gotcha. "How I finally centered a div, and why it works."
  • News. Something new in AI or tech worth two minutes of everyone's attention. "What this week's model release changes for how we build."
  • Discussion. A question you are stuck on, or an idea you want the class to weigh in on. "Is it cheating to let AI write the whole thing? Let us talk it through."

🙌 You Can Absolutely Do This

The usual reason people skip a lightning talk is a small voice that says they have nothing to offer. That voice is wrong. Here is what it tends to say, and why it is wrong:

  • "Everyone already knows this." They do not. They think they do, but you understand it better, and they will pick something up. Even if they know it, hearing another person explain it is useful.
  • "I am not an expert." You do not have to be. You only have to be interested enough to talk for two minutes. You know more than you think.
  • "Speaking in front of people is scary." True, and you will feel great once you have done it. Everyone is nervous, even the people who look calm. You can even carry the talk by walking through a demo instead of speaking the whole time.
  • "My idea is not good enough." It is better than you think. There are really no bad ideas for a lightning talk.

✍️ How to Sign Up

  1. Open the Lightning Talks board on the course site.
  2. Sign in with GitHub, the same account you use for your sites.
  3. Pick an open day and a category. The topic can wait.
  4. Lock in your topic by the day before your talk, so the instructor can plan the run of show. For your second talk, include the URL of the page you will present from.

New dates open about two weeks at a time, since the schedule can shift, so check back if you do not see the day you want yet. You can change your day or topic, or cancel, any time before your talk.

Claim your first slot early. Waiting until the back half means both of your talks land in the same crowded stretch of the semester.

🎯 Preparing Your Talk

Two minutes is shorter than it sounds, and most first-time presenters try to cover three times what fits. A few notes before you build anything:

  • One idea, one takeaway. Decide the single thing you want the room to remember, then build everything around it.
  • Plan for about ninety seconds of content. The rest gets eaten by setup and the one thing you forgot.
  • Open with a hook. Give the room a reason to care in your first sentence.
  • Show, do not tell. A quick demo or a screenshot beats a wall of words, and it helps everyone recognize the idea next time.
  • Rehearse out loud, with a timer. Reading your slides silently will not reveal where you run long.
  • Write the discussion question down before you rehearse. If you leave it to the moment, you will ask something everyone agrees with and the two minutes will die.
  • If something breaks, keep going. Slides fail to load and demos stop cooperating. Working through a hiccup in front of a room is its own useful skill, and the room is on your side.

📚 Resources

A few of the best short reads and watches for first-time presenters:

Last updated: Sunday, 8/23/2026