← Back to Part 2

Part 2 · Vibe Coding

Instructor notes

How to run the class. Students are welcome to read this too.

Guidelines

  1. 1. Welcome: What Is Vibe Coding?

    • Show a 60-second live demo: type one sentence, get an app. It sets the mood.
    • Ask: 'Who has never written code?' Celebrate the raised hands; this class is for them.
  2. 2. Pick Your Tool

    • Recommend one tool for the room so you can help everyone. Mixed tools slow the class down.
  3. 3. From MVP Brief to Build Brief

    • Walk the room and cut scope ruthlessly. Most students list 10 screens; push them to 3.
  4. 4. Your First Build

    • Build GuardianLine live on the projector at the same time.
    • While builds run (1–2 min), ask volunteers to share their 'magic moment' out loud.
    • Expect gasps. Give people a minute to enjoy it before moving on.
  5. 5. Iterate: One Change at a Time

    • This is the longest block. Take a 5-minute break halfway through.
    • Demo a deliberate mistake and a fix, so students learn recovery is normal.
    • Watch for students stuck in 'fix loops'.
  6. 6. Make It Real: Data & Logins

    • Stress privacy before anyone adds logins.
  7. 7. Test It With a Real Human

    • Enforce the 'no talking' rule. It's hard and it's the whole lesson.
    • Collect one surprising finding per pair to share in the wrap-up.
  8. 8. Publish, Demo & Next Steps

    • Time-box demos strictly: 30 seconds each, or pick 5 volunteers in a big class.
    • Close the loop: Part 1 found the concept, Part 2 made it real.
    • Share a follow-up channel (email list, community) for questions after class.