Skip to content
Ship Your First Thing

Lesson 01 · 15 min · updated May 9, 2026

Welcome

Learning objective

By the end of this lesson, you will know what this course is, who it's for, what you'll have built when you finish, and how to read the rest of Module 0.

Why this matters

Most coding courses promise too much and deliver something close enough to feel like a win without actually being one. This course tries hard not to do that. Knowing the shape of what you're signing up for — what you'll learn, what you won't, what it'll cost, and where the hard parts are — is the difference between finishing and quitting at Module 3.

Core read

Welcome. Briefly:

This course is Ship Your First Thing. It's an open-source, self-paced course for people who have never written production code and want to build a real, working product anyone on the internet can visit. By the end, you will have built a small social platform — sign-up, profile, posts, follows, feed, comments, likes — running at a public URL.

There are two surfaces:

  1. The course material — the words you're reading right now, written in markdown (a way of writing formatted documents using simple punctuation marks, → GLOSSARY). This is the canonical source. It lives in a public GitHub (a website that hosts code repositories and runs developer tools on top of them, → GLOSSARY) repository so anyone can fork it, contribute to it, or read it offline.
  2. The course platform — a web app at shipyourfirstthing.com that renders the same lessons with personalized features (sign-in, progress tracking, comments, bookmarks, completion certificate). The platform is built in a separate phase of this project; for now, focus on the course material.

Who this course is for:

  • You're comfortable using a computer.
  • You've never written production code.
  • You may have seen GitHub before, but only as a viewer.
  • You're curious about building real software.
  • You're a little intimidated by code.
  • You may or may not have budget for paid AI coding tools — this course handles all three honest cost paths.

If that's you: welcome.

Who this course is not for:

  • People who already write production code professionally — this will be too slow for you.
  • People who want a fast, no-friction tutorial — this course is honest about friction.
  • People who want a guarantee — there are none here. The skill you'll learn is the loop: noticing when the AI is wrong and steering it back. Recovery, not happy paths.

What you'll have when you finish:

  • A working social-platform thread project running at a public URL anyone on the internet can visit.
  • A working mental model of how software is built — you'll meet the technical names for these pieces in Module 1.
  • Real fluency in working with an AI coding agent (a program that reads your project files and writes code on your behalf based on a conversation with you, → GLOSSARY): planning, executing, recognizing wrong output, recovering.
  • A short shelf of habits — saving your work often, testing with multiple sign-ins, watching what your AI tool charges per session — that are durable across whichever AI tool you use next.

What this course is honest about:

  • AI tools change every few months. This course is written so the loop outlives the keystrokes. When you see the date stamp on a lesson and it's a year old, check WHAT-CHANGED.md first; the keystrokes may have shifted, but the loop won't have.
  • The free path is real and capped by rate limits. The paid path is predictable and costs ~$20/month. The "token-careful" path is cheap if you're careful and ruinous if you're not. Module 0 lesson 03 walks you through the triage.
  • You will get stuck. The course expects this. COMMON-ISSUES.md is where you go when reality drifts from a lesson.

How to read this course:

  • Read in order. Module 0 → Module 1 → Module 2 → ... → Module 7. Skipping Module 1 (mental models) to get to "the building" is the most common way learners stall in Module 3.
  • Do the exercises. Each lesson ends with a 10–25 minute concrete exercise. Skipping exercises is how recognition (I've read this) fails to become recall (I can do this).
  • When you're stuck, check COMMON-ISSUES.md, then WHAT-CHANGED.md, then file an issue.

That's the whole course in two paragraphs. Module 0 spends the next four lessons getting your environment ready. Then Module 1 builds the mental models you'll use forever. Then Module 2 introduces the toolchain. Then we build.

Exercise

Spend 5 minutes on each of these:

  1. Open BUDGET.md and skim the three named cost paths. Don't pick yet — lesson 03 walks the triage. Just know they exist.
  2. Open WHAT-CHANGED.md. Read the V1 baseline entry. This file is your friend when reality drifts from a lesson.
  3. Open modules/01-mental-models/README.md. Read the four bundle titles. This is what Module 1 covers, and it is the most-skipped module in courses like this. (Don't skip it.)

Checkpoint

You've got this if you can:

  • Name the three cost paths from BUDGET.md in one phrase each.
  • Say where you'd look first when something in a lesson doesn't match what you see (WHAT-CHANGED.md, then COMMON-ISSUES.md).
  • Name the four Module 1 bundles without re-opening Module 1's README.

What you just did

You took five minutes to know the shape of the course before installing anything. That single habit — "what am I getting into?" before "what's the next button?" — is the closest thing this course has to a mantra. You'll use the same habit before every AI prompt in Module 3.

Sign in to track your progress through the course.