Demo Fair: Ship It
Pitch your favorite project from the week, show what changed because of feedback, and take stock of everything you built.
🎉 The Demo Fair
This is it — pick your favorite project from the entire week, whichever one you’re most proud of, and get ready to show it off.
Every pitch covers the same three things, in whatever order feels natural:
- Who it’s for — your Day 2 PM answer
- What it does — the one thing it does well
- What changed because of feedback — the rose and thorn from Day 3, and the change you made
That third point is the one first-time builders usually skip, and it’s the most interesting part of the story. “I built a quiz” is a fact. “I built a quiz, and someone almost missed the whole point of it until I fixed the hover state” is a story about how you actually build things — describe, test, learn, refine.
Don’t open your pitch with “sorry, it’s not done” or “this part doesn’t really work.” Every project in this room is a snapshot of three days of learning, not a finished product. Show what it does, own what you built, and mention what you’d do next if you had more time — that’s confidence, not perfection.
🔁 Three Days, One Loop
Take a second to notice what actually happened this week:
| Day | What you added | What stayed the same |
|---|---|---|
| 1 | The vibe coding loop and the prompt template | — |
| 2 | The PM lens (who / what) and three UX habits | Describe → Build → Test → Refine → Repeat |
| 3 | Real feedback from someone else’s eyes | Describe → Build → Test → Refine → Repeat |
The loop from Day 1 never changed. Every new lens just made each lap of that loop sharper — a more specific prompt, a more focused build, a fix aimed at something a real person actually struggled with. That’s the whole skill: not memorizing syntax, but getting better at describing, testing, and refining.
You can run this exact process on anything next — a flight-planning tool, a study tracker for your next exam, a page for a club you’re part of. The tool might change. The loop won’t.
A friend outside this workshop asks you what 'vibe coding' actually means, in one sentence. What's the most accurate answer, based on everything you practiced this week?
Reveal Answer & Explanation
It’s describing what you want in plain English, letting an AI write the code, and steering the result by testing it and asking for specific changes — repeated until it works.
The “vibe” isn’t about being vague — your best prompts this week were specific about audience, purpose, and detail. It’s about not needing to know the underlying code yourself; you steer through description, testing, and refinement instead of typing syntax directly. That loop — Describe, Build, Test, Refine, Repeat — is the actual skill, and it works whether you’re a complete beginner or an experienced programmer.
👋 Before You Go
- Make sure your favorite project is saved in the shared Drive folder under the right day and version number
- Take a photo of your screen if you want a personal souvenir of what you built
- Certificates and any small prizes get handed out now — you earned them
Congratulations — you spent three days building real, working software with nothing but a browser, a Google account, and a way of thinking that scales far beyond this room. Fly safe, and keep building.
🎁 Optional: Take It Further
Want your favorite project to live at a real web address instead of a saved file? The next lesson is a short, optional walkthrough of putting it online for free with GitHub Pages — no pressure, read it whenever you’re ready.