Module 2 · Week 1 · Days 4–5 Not started

Shipping pipeline: put it on the internet

Get v1 onto a public link, and build a way to ship updates safely and tell people what changed.

The brief

Make it live at a real address that you can text to a friend. Then improve one thing and ship it through a process you could repeat with your eyes half closed. Tell people what changed.

Why this matters

Something that only runs on your laptop doesn’t exist yet. Shipping is where most side projects die, so you’re going to make it boring and safe instead.

Where to start

Ask Claude which free hosting option fits your project. Vercel, Netlify and Cloudflare Pages are all good. Let it set things up, but make it explain each step.

Once you’re live, make a small change and practise the full loop: make the change, preview it, check it works, publish it, write one line about it for users.

“How do you know it works?” is the question your reviewer will ask every time. Have an answer before you hit publish.

What your reviewer will look for

These come up in almost every review of this module. Get ahead of them.

Shipping without checking first.
Release notes that read like a commit log instead of news for users.
Panic when something breaks. Breaking things is normal; not knowing how to undo is the problem.

Skills this module tends to surface:

Verifying Debugging with AI Context management

Submit for review

Fill this in, copy it, and post it in the cohort channel. Reviews focus on your process as much as the result, so be honest about where you got stuck.