Skip to content
Page 7 of 7

Reflection 4

How This Reflection Works

Your Facilitator will pull from these questions to lead a cohort-wide discussion. If your AI assistant is building during a Challenge and you have a free moment, these also make great team conversation starters while you wait.

What You Shipped

  • Your app is live. What was the moment like when you opened that URL for the first time outside your workspace?
  • What's the feature you're most proud of in the final product? Is it something from Challenge 1, something you added along the way, or something you built in this final sprint?
  • If one of your app's intended users opened it right now, what would they get out of it? What's still missing?

What You Practiced

  • Lesson 4 introduced the idea that deployment is "one prompt away." Did it feel that simple in practice? What surprised you about the process of going live?
  • Think about the risks Lesson 4 raised: the two-week cliff, the validation gap, the importance of authoritative data sources. Did any of those feel real during this challenge? Did you catch something that "looked done" but wasn't quite right?
  • Across all four lessons, you learned prompting (Lesson 1), file access (Lesson 2), context (Lesson 3), and deployment (Lesson 4). Which of those skills made the biggest difference in what you were able to build?

The Full Journey

  • Think about your first prompt in Challenge 1, the very first thing you asked AI to build. Compare that to what's deployed right now. What changed, and what changed in you?
  • Was there a moment where something clicked, where the way you work with AI shifted from awkward to natural?

What Comes Next

  • Lesson 4 made the point that AI lets you produce faster, and the choice is whether to invest that speed into more output or more understanding. Looking back at today, which did your team lean toward? Which would you lean toward on your next project?
  • After today, what's one thing you might build with AI? A tool for your job? Something for your family or community? A side project that's been rattling around in your head?
  • One way to think about what you learned today: your role isn't just "person who tells AI what to build." It's more like a gardener. You set up the environment (context files, rules, user stories, verification habits) and AI grows the software inside those constraints. What would your "garden" look like for your next project?