Make your public work strategically deliberate instead of accumulated. Distinguish what compounds from what doesn't. Own your distribution. Develop voice as a decade-scale asset — and install the publishing system that keeps it alive. Public writing is a write-ahead log of your thinking: years of WAL produce a queryable history, and strangers binary-search it to arrive at your door pre-sold on your judgment. The audience is a cache other people warm on your behalf — when you pitch, apply, or launch, the conversation starts at the second hop. Owned distribution is the difference between durable storage and someone else's volatile memory: the feed is RAM — fast, lossy, evicted in days; the domain-plus-list is disk — slow, replicated, forever. Engineers who write only to RAM end their careers with nothing queryable. And the OSS audit is portfolio rebalancing under a maintenance budget: every project is a position with carry cost, and the flagship-with-supporting-cast allocation beats the index of neglected positions every time.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The two earlier drafts of this curriculum wrote this module for two different readers, and the merge keeps both because you'll be both at different times. One draft wrote for the …
You may already be doing public work — a package with real downloads, scattered posts, a portfolio site, talks given and forgotten. What most engineers never do is look at the acc…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Approach: Reference
Approach: Reference
1. The why-audit. Thirty minutes, honest, ranked. The top reason should be a sentence you'd say to a friend who'd see through hedging. Then check: do your activities match your in…
11 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.