Establish the sustainable infrastructure of a teaching practice — owned platform, newsletter, publication cadence, audience model — and write the capstone document: the explicit, falsifiable plan for the teaching practice you will run for the next five years, kill criteria included. The capstone is the architecture decision record for your teaching practice: decision, alternatives considered, rationale, consequences, revisit date. Engineers who try to write a "personal mission statement" produce something unreadable; engineers who write an ADR produce something useful. Use the form you already know. And the practice itself is a service you operate: the cadence is the SLO, the newsletter list is the customer database you own, the domain is the origin server, rented platforms are CDNs. Audience growth follows compound-interest dynamics, not linear ones — which means you must survive Year 1 (low growth, high effort) to reap Year 3, when the back-catalog compounds. Most engineers quit in Month 8. The kill criteria exist so that stopping is also an engineering decision — made against pre-committed thresholds, not against a bad week.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The compounding is real and most engineers quit at month 8. That sentence is half this module; the rest is a slower way of saying it, plus the document that makes it survivable. A…
A teaching practice that depends on continuous external validation does not survive Year 2. A practice that lives only on rented platforms is a tenant at the landlord's mercy. A p…
Approach: Essential
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
1. Infrastructure up: newsletter established (Buttondown, Kit, or similar — the list is the asset, owned by you, exportable), welcome message written, any existing audience import…
8 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.