Skip to content
Page 1 of 7

Lesson 2: From Chat to Code

Where We're Starting

In Lesson 1, you proved something important: you can describe what you want in plain English and AI will build it. You used that skill in Challenge 1 to create an Expedition Safety Brief, a real, interactive planning resource you built entirely by talking to AI.

But you probably noticed something: the alert status is hardcoded, the weather data is made up, every change means re-generating the whole thing from scratch, and there's no way for your team to build different parts at the same time. You built something real, but chat has real limits.

This lesson bridges that gap. You're about to move from a chat interface into a real development environment, one where your work lives as files, connects to real data, and persists between sessions. Same prompting skills. New superpowers.

You completed Challenge 1 and proved you can build with AI. Now check in on where you are between these two levels:

  • Dabbler. You've tried AI tools out of curiosity, but AI isn't part of how you work day to day.
  • Doer. You use AI regularly to get things done. You can write effective prompts, build with AI assistance, and troubleshoot when things go sideways.

Your slider value moves your avatar on the progress board. Be honest about where you feel right now.

What You'll Learn

By the end of this lesson, you'll understand what changes when you move from chat to a real development environment, and you'll be ready to put it to work:

  • Why chat tools have limits and what a development environment gives you
  • What a codebase actually is (it's simpler than you think)
  • What becomes possible when AI can read and write files: real data, real apps, real persistence
  • How to explore and navigate your project using AI

Sections

  1. From Chat to Code - Why you're making this transition and what it unlocks
  2. Your Code is Just a Folder of Files - Demystifying the codebase - it's a recipe book, not rocket science
  3. What File Access Unlocks - Real data, real apps, real persistence
  4. Bringing Your Prototype Home - Migrate your chat prototype into your project and explore what's there

By the End of This Lesson

  • You can explain what a codebase is and why version history matters
  • You've made your first change and used Save & Sync to protect your work
  • You understand what file access makes possible that chat couldn't do
  • You've migrated your Challenge 1 prototype into your project
  • You know what's real and what's hardcoded in your Challenge 1 prototype, and you're ready to fix that in Challenge 2