Write a paragraph a stranger can read once and understand. Then write a 1,200+ word piece a stranger will finish and remember a week later — and publish several of them. Writing is refactoring. The first draft is the first commit. The second pass is the code review you give yourself: "this paragraph is doing two things — split it." The third pass is the performance pass: "this sentence allocates eight words where four would do." The curse of knowledge is the bug where your README assumes the reader already knows what the package solves. Given-new flow is dependency ordering. And the single-responsibility paragraph is the most reliable rewrite test in English: one paragraph, one summarizable idea — run that check on everything you publish and you will outrun ninety percent of engineers writing online.
This course unlocks once you've finished its prerequisite. Open prerequisite →
If you only do one module of this curriculum, do this one. Everything else is a derivative work. A talk is writing performed. A pitch is writing compressed. A difficult conversati…
Writing is the thinking tool, not just the communication tool. The act of putting a complex idea into a paragraph is the act of finding out whether you actually understand the ide…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Approach: Reference
Approach: Reference
Publish four 1,200+ word pieces over six to eight weeks on a site you control (your own domain preferred; a platform is acceptable as syndication). Two technical (a lesson from a …
12 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.