There’s a specific kind of person the Builder track is built for: someone who writes prose for a living, has tinkered in spreadsheets, and has looked at a JavaScript file twice and backed away slowly. You don’t need to become a software engineer. You need enough confidence to ship one small thing. That’s what the track delivers.
The core insight
Most “learning to code” advice overshoots. It treats you as a future full-time engineer. You’re not. You’re a person who wants an iPhone Shortcut that triages their Calendar, a Python script that reconciles two CSVs, or a tiny Cloudflare Worker that posts a reminder every morning. You want to finish one thing. AI can do the syntax. Your job is the shape.
The daily loop
A Builder quest is 10 minutes of pairing with Claude, Cursor, or Copilot against a real (small) problem:
- Describe what you want in one sentence, in plain English.
- Ask the model to sketch the 4–6 steps, no code yet.
- Approve or correct the steps.
- Ask for code for step 1 only. Run it. Fix it.
- Repeat for step 2. Stop when the thing works, not when the thing is pretty.
After ten days you’ll have shipped something. Not a product. A thing that does one job.
Three examples
The iPhone Shortcut you’ve wanted for years. “When I tap this, ask me ‘what are you doing tomorrow,’ take my answer, and add a calendar entry with a 15-minute blocker 30 minutes before.” Five lines of Shortcut config; you’ll get there in two sessions.
The CSV reconciler. You have two spreadsheets that almost but don’t quite match. A 50-line Python script spots the mismatches. You’d have spent a Sunday doing it by hand.
The little Cloudflare Worker. A tiny Worker that reads a public API every morning and posts a summary to your phone via a Shortcut. You’ll understand what a Worker is by Thursday.
What to watch for
- Don’t aim for reusable or “production-grade” code. It’s your code. If it works today and you’d rewrite it in six months, that’s fine — you’re not going to have to.
- AI will confidently produce broken code. Run every snippet. If it fails, paste the whole error back. Don’t try to interpret it yourself at first.
- The hardest part is shipping, not coding. Your blocker will be fear, not syntax. The track counters this by making each quest small enough that shipping is faster than abandoning.
Where to start
The Builder track opens with a “Hello, iPhone Shortcut” quest. If you’ve never touched Shortcuts, that’s the right place. If you have, Quest 3 is a “read someone else’s code” drill that will double your reading speed in a week.