The full curriculum, for browsing.

The acknowledgments, the dedication, the read-me-first. If you've never opened this curriculum before, sections 0.4 and 0.6 are the ones that decide where you go next. Part 0 also now carries Internet Menace Foundations: the original v1 curriculum (July 2024), reorganized here as sections 0.7 through 0.17. If you already finished v1, you can skip straight to Part 1.

The argument for why the original Internet Menace foundation matters more in 2026, not less. The case against the loudest grift in tech right now ("AI will write code for you, you don't need to learn programming"), and the working definition of vibe coding this curriculum will use throughout. If you read one Part before deciding whether the rest is for you, read this one.

The four-stage pipeline from idea to working software: requirements, specs, structured prompts, agent execution. Most of the people who can't ship are stuck because they're trying to do all four stages at once in their head; this Part separates them.

The actual software you'll work with: editors, coding agents, voice-to-text, data pipelines, API generators, agent frameworks. Strong opinions on which tools are worth your time and which ones you can ignore for now.

When to spend $200 a month on a frontier model and when to spend $0 a month on hardware in your closet. The math, the trade-offs, and the vocabulary you need to read a model's spec sheet without nodding along to things you don't understand. Sections 4.2, 4.3, and 4.5 are deep-dives; you can skip them on first pass and come back when you're buying hardware.

How to describe a piece of software clearly enough that an agent can actually build it. Data shape, layout vocabulary, component vocabulary, design preferences, user roles, API design, all the parts that beginners skip and then can't figure out why their agent's output keeps missing the mark.

The discipline that separates people who ship working software from people who confidently ship broken software. Reading code you didn't write, git as a seatbelt, the verification habit, secrets management, data privacy, and what production deployment actually looks like for a small business. The most underrated Part in the curriculum, and the one most readers skip first.

Four worked loadouts: the roofer, the restaurant manager, the solo consultant, and the data analyst leveling up from v1. Pick the one closest to your situation and read that section first; the others are useful as reference, not as required reading.

Nine templates in three categories: spec-writing (PRD, feature spec, CLAUDE.md), project types (small business site, internal dashboard, API skeleton), and agent crews (Gmail+Calendar, customer scheduling, inventory and reorder). Copy one, adapt it, ship the thing; if the right template doesn't exist yet, see section 9.2.

What "functional" looks like now, where to find the rest of the people doing this work, and how to send back what you build so the next person doesn't have to figure it out from scratch. The closing argument; read it when you've done enough of the work to recognize yourself in it.