Your Code Can Talk.
Can You?

Before you show a single screen, answer the question your audience is already asking silently: "Why should I care about this?" Open with the problem that motivated the app — a frustration, a gap, a moment of curiosity. Make the audience feel the need before you present the solution. Once they feel the problem, every feature you demo carries emotional weight.

The most memorable presentations follow a narrative arc: What is (the status quo and its friction) → What could be (your app's possibility) → How we get there (the demo and the learning). Audiences are wired for story. When you present features as bullet points, the brain stores them in working memory and discards them. When you wrap them in narrative, they stick.

Steve Jobs never spent the first ten minutes explaining what the iPhone was going to do. He showed it. Show your app doing its most impressive thing within the first three minutes. You'll capture attention when it's at its highest, and the rest of the talk becomes explanation of something the audience already wants to understand. Always have a backup — a screen recording, screenshots — for when live demos break.

You have spent weeks with this code. You know what "the state object" means, why you chose that API, and what a callback is. Your audience may not — and even if they do, they haven't lived in your codebase. The "Curse of Knowledge" is the cognitive bias that makes experts forget what it felt like to not know something. Fight it consciously: define your terms once, use analogies, and never assume shared context.

You didn't write every line — and that's the point. The most intellectually honest and genuinely interesting thing you can do is explain how you collaborated with AI. What prompts worked? Which outputs were wrong and how did you know? What did the AI teach you inadvertently? Showing that you can critically evaluate, debug, and assimilate AI-generated code is a far more sophisticated skill than writing it yourself. Make that case out loud.

The instinct under pressure is to rush. Filling every gap with "um," "like," and "so yeah" signals anxiety to your audience and obscures your competence. A deliberate two-second pause after a key point lets the idea land. Research from Harvard psychologist Amy Cuddy shows that even your own perception of your competence changes when your body language and pace project calm. Slow down. Breathe. You earned the room.

A slide packed with bullet points tells the audience to read, not listen. The moment they read, they stop hearing you. Follow the principle of "one idea per slide" — use visuals, screenshots, and short phrases as cues, not scripts. If you can read your entire slide aloud without adding anything, the slide is doing your job and you're redundant in the room. Be the insight; let the slide be the anchor.

Your teacher will ask about implementation decisions. Your peers will ask "did you think about doing it this way instead?" The worst Q&A responses are defensive ones. Prepare three categories: (1) Questions you know cold, (2) Questions you partially know (say what you know, name the gap), (3) Questions you genuinely don't know yet (say "I don't know, but here's how I'd find out" — this is an intellectually mature answer).

The most effective tech communicators — from Richard Feynman to Sal Khan to the best TED speakers — use humor deliberately. It is not frivolous. Laughter releases dopamine, which improves memory retention in your audience. You don't need to be a comedian. Self-deprecating honesty about a bug that stumped you for three days, a prompt that returned something hilariously wrong, or a feature that "works on my machine" lands exactly right with a CS audience. Lean into it.

Running through your talk silently in your head produces a false sense of readiness. The mouth, the voice, and the cognitive load of speaking are entirely different systems. Stand up. Say it out loud. Time it. Record yourself once — watching playback is uncomfortable, but it is the single highest-ROI practice technique available. Your voice will change, your pace will slow, and your transitions will sharpen in ways that silent rehearsal never achieves.