You're About to Build Software¶
The Big Idea¶
Here's something that would have been unbelievable five years ago: you don't need to write code to build software.
AI chat tools (the kind you can open in a browser right now) can take a plain English description of what you want and turn it into a working application. Not a sketch. Not a mockup. A real, interactive thing that runs in a browser.
This changes who gets to build things. It used to be that if you had a great idea, you needed to find a programmer, explain your vision, wait, give feedback, wait more, and hope the result matched what you imagined. Now, you describe what you want, and AI builds it while you watch. If it's not right, you say what to change. The whole loop takes minutes, not weeks.
We call someone who can do this a full stack builder: a person who can identify a problem and build the solution, regardless of their job title. You don't need to become an engineer. You need to learn how to direct an AI that builds on your behalf, the same way you might direct a capable colleague by describing the outcome you want rather than doing every step yourself.
What You'll Build Today¶
After this lesson, your team is going to build an Expedition Safety Brief: a real, interactive planning resource for backcountry hikers heading into the Greater Yellowstone Ecosystem.
Think: active park alerts, weather forecast, river crossing conditions. Everything a hiker needs to plan a safe route before leaving the trailhead.
You'll build it entirely by talking to an AI chat tool. No code. No terminal. Just you, your team, and a conversation with AI.
But first, you need to learn how to have that conversation well. That's what the rest of this lesson is about.
Throughout this lesson, you'll practice with small experiments: quick, disposable exercises to build your prompting muscles. Think of them as sketches, not the final painting. Start a fresh conversation for each one so you're working with a clean slate every time. Your real build starts after the lesson.
Choose Your Team Name
Team Discussion | ~2 minutes total
You're about to build something together. Every great team needs a name.
Come up with a team name you'll use for the rest of the challenge. It can be ridiculous, event-themed, tech-flavored, or completely random. You can always change it later, but pick something now.
Once you have it, write it somewhere everyone can see it. It's yours for the duration of this lab.
Key Insight
Software creation is no longer gated behind specialization. If you can describe what you want clearly enough, you can build it. The skill you're learning today, how to communicate with AI effectively, is the skill that makes that possible.