→ From Coder to Shipper
COURSE OVERVIEW · 12 DAYS

From Coder to Shipper

Take a project all the way from “I have an idea” to “a stranger on the internet can use it.”

12 days · 3 times a week · about 1 month · 2–3 h per lesson

1
SECTION 01

Who it's for

A short, honest pitch before the plan.

THE STUDENT

You bring the code. We build the rest of the path.

You bring

A real coder: comfortable in JavaScript, can read Python, has used cd and ls. You write and understand code — that part is already done.

You're missing

Everything between “code is done” and “it's live”: a server, a domain, DNS, HTTPS, a database, containers, ops — the whole shipping path.

AFTER DAY 12

What you can actually do

Own a VPS end to end

Provision it, harden it, keep it running while you sleep.

Name plus trust

A domain, DNS, and a 90-day auto-renewing HTTPS cert.

A real web app

Flask plus SQLite, containerized with Docker, behind nginx.

Features that cost money

Payments, transactional email, and AI behind one API.

See it before users do

Uptime checks, metrics, dashboards, alerts.

A portfolio that ships

A capstone: your own idea, live on your own domain.

2
SECTION 02

The big picture

One diagram, hammered until it becomes instinct.

THE MENTAL MODEL

The path in one picture

Every day of the course adds one more hop you can narrate.

01
Idea
you already have it
→
02
Terminal
the OS remote control
→
03
VPS
your box on the internet
→
04
DNS
name becomes address
→
05
TLS
the lock icon
→
06
nginx
the front door
→
07
Flask + SQLite
app plus data
→
08
Docker
ship the box, not the code
→
09
Live URL
a stranger can use it
HOW WE TEACH

Five habits behind every slide

The full path is the skill

Idea → terminal → VPS → DNS → nginx → HTTPS → live. You should narrate every hop.

Raw first, then abstract

Install with apt, run with systemd, edit files by hand — then see Docker package all of it.

AI accelerates, you operate

AI writes a lot of the code. You read it, review it, tweak it, ship it, own it.

One idea per slide

Demoed live in the playground: curl the endpoint, watch the log, break it on purpose.

A live artifact every day

A reachable URL, a service that survives reboot, a cert that renews itself.

“The full path is the skill. If you can narrate every hop from idea to live, you are a shipper.”
— the one rule of the course
3
SECTION 03

The platform

One login, everything you need for the whole course.

EVERY STUDENT LOGS IN TO

One platform, three instruments

Every slide deck in this course is published on the same platform.

Playground environment

A live sandbox mirroring the course stack — terminal, editor, a VPS-style box. Copy code from any slide straight in.

Auto-graded homework

Instant pass or fail on every day's exercises — iterate at your own pace between the 3 weekly sessions.

Guiding chatbot

Course-aware: explains any slide, nudges stuck students, never gives away the answer.

DAY 1, IN THE PLAYGROUND

Your very first real session

ops@vps — zsh
$ ls
app/ data/ notes.md
$ cd app && python main.py
* Running on http://127.0.0.1:5000
$ curl -s http://127.0.0.1:5000/api/health
{"ok": true}
A TYPICAL 2–3 H LESSON

How a day actually runs

  1. 1

    Review — about 15 min

    Chatbot-recapped homework results; yesterday's blockers cleared.

  2. 2

    Decks — 60–90 min

    One to three related decks, one idea per slide, key points demoed live.

  3. 3

    Guided lab — 45–60 min

    Build the day's live artifact in the playground; you narrate the path yourself.

  4. 4

    Homework — 15 min

    Auto-graded, due before the next session, rehearses tomorrow's decks.

FROM THE DECKS · FLASK & HTTP

The app you'll build by day 6

A Flask route, a database read, one JSON answer — highlighted exactly as in the deck.

app.py
# app.py — born day 4, live by day 6
from flask import Flask, jsonify

app = Flask(__name__)

@app.route("/api/health")
def health():
    n = 42
    return jsonify(ok=True, users=n)
FROM THE DECKS · GIT & DOCKER

The session that makes it live

Commit, push, rebuild, verify — the same four moves, every single day.

bash
# day 6 — the first full ship
git add app/ && git commit -m "wire up /api/health"
git push origin main
docker compose up -d
curl -s https://shop.example.com/api/health
{"ok": true, "users": 42}
FROM THE DECKS · DOCKER & NGINX

The whole site in one file

Compose declares the goal; the machine keeps it true.

docker-compose.yml
# the whole site, one file
services:
  web:
    image: shop:v2
    ports:
      - "8080:80"
  db:
    image: sqlite-store
    volumes:
      - data:/var/lib/shop
volumes:
  data:
4
SECTION 04

The 12-day plan

27 topic decks across 11 teaching days. Day 12 is the finale.

THE TIMELINE

12 days, 4 weeks, 3 a week

Only 11 days carry teaching content — Day 12 is reserved for the finale.

WEEK 1
D1
Kickoff & your tools
speakers (1 h) · terminal · text-editor
D2
The client side
frontend
D3
The language
python-basics · python-libs
WEEK 2
D4
App plus data
flask-http · sqlite
D5
History & packaging
git · python-advanced · package-managers
D6
Pack it, door it
docker · nginx
WEEK 3
D7
Name, address, trust
internet · systemd
D8
Harden & monetize
backend-security · email · payments
D9
AI plus ops
llama-server · observability · vpns
WEEK 4
D10
Beyond, rapid-fire
cdn · k8s · ci-cd · object-storage · message-queue
D11
Capstone prep
game-dev · mobile-dev · capstone prep
D12
Capstone day
demos · speakers · employers
DAYS 1–6

Weeks 1–2: build the stack

DayThemeDecks
1Kickoff & your toolsspeakers (1 h) · terminal · text-editor
2The client sidefrontend
3The languagepython-basics · python-libs
4App plus dataflask-http · sqlite
5History & packaginggit · python-advanced · package-managers
6Pack it, door itdocker · nginx
DAYS 7–12

Weeks 3–4: go live, then show off

DayThemeDecks
7Name, address, trustinternet · systemd
8Harden & monetizebackend-security · email · payments
9AI plus opsllama-server · observability · vpns
10Beyond, rapid-firecdn · k8s · ci-cd · object-storage · message-queue
11Capstone prepgame-dev · mobile-dev · capstone prep
12Capstone day — no teachingdemos · 2–3 guest speakers · employers
“Eleven days of building. One day of showing off — with employers in the room.”
5
SECTION 05

The capstone

Not an exam. A product.

YOUR PROJECT, YOUR DOOR

From “I have an idea” to a live URL

What it is

Your own project, end to end: a real domain, an HTTPS lock, Flask plus SQLite behind nginx, running in Docker on your VPS.

How you get there

Every day's homework and lab build toward it. Day 11 is dedicated capstone prep. Day 12 is the stage.

DAY 12 — THE FINALE

No teaching. Just showing off.

Demo your capstone

Idea to live site, narrated by you. The whole cohort watches.

2–3 guest speakers

Practitioners on shipping, scale, and careers — the industry's side of the story.

Meet potential employers

Structured meetings with companies that saw what you built in 12 days.

6
SECTION 06

Your move

READY WHEN YOU ARE

Ready to ship?

12 days, 3 times a week, about 1 month. On the other side: one live product on your own domain.

All materials live on the course platform — playground, auto-graded homework, chatbot included.

From coder to shipper.

12 days. Three sessions a week. One live product.