Learn Tech Writing with Phoebe

Docs people actually use

You know the pain: the undocumented repo, the on-call engineer guessing at 2am, the wiki page nobody reads twice. This course is the fix - a practitioner's technical-writing method for data and AI teams, built from the same free sources Google trains its own engineers on. Across eight sessions you document one real pipeline end to end, and walk away with a documented system plus a repeatable method. Every session is 45 minutes live, with self-study depth for after class.

8sessions
4deep dives
9official sources
1running project
One project, eight sessions. Every session documents Pulse - a small CSV-to-metrics pipeline that ships in this repo at pulse/ with working code and zero documentation, on purpose. Session by session it gains a README, a how-to, reference pages, ADRs, a changelog, Vale linting in CI, and an edited v1.0 doc set you'd be proud to inherit. Honest about scope: certificates and the facilitated in-class exercises stay with the free official sources, starting with Google's technical writing courses.

The sessions ✍️ · for practitioners · 8 x 45 min

From the audience equation to a shipped v1.0 - each session teaches the craft on real source material, then applies it to Pulse in a build-along.

🎯 Session 1 · start here

Why docs fail: the audience equation

The good-docs formula behind every writing decision, scope statements that win the 30-second scan, and your first look at Pulse.

▶ Start hereThe formula
✂️ Session 2 · easy

Sentences that work

Active voice, one idea per sentence, and the words to cut - then the rescue of Pulse's unreadable NOTES.txt.

Active voice
📋 Session 3 · easy

Structure readers can scan

Lists, tables, paragraphs, and headings - the shapes that let a busy reader find one answer without reading everything.

Lists + tables
🚪 Session 4 · core

The README: milestone 1

The project's front door, assembled from everything in Sessions 1-3: Pulse gets a full README a newcomer can actually follow.

Milestone 1
🧭 Session 5 · core

Diátaxis: the four kinds of docs

The map that ends "where does this go?" forever - tutorials, how-tos, reference, explanation - plus Pulse's first how-to guide.

The map
🗄️ Session 6 · deeper

Reference, ADRs, changelogs: milestone 2

The project's memory: a config reference, the decision records that explain "why UTC everywhere", and a changelog that keeps its promises.

Milestone 2
⚙️ Session 7 · deeper

Docs as code: milestone 3

Docs in git, reviewed like code, linted by Vale in CI - the workflow that keeps a doc set alive after the enthusiasm fades.

Milestone 3
🚢 Session 8 · full stack

Edit like a pro, ship v1.0

The self-editing pass, caption-first diagrams, where LLMs help and where they hurt - then Pulse's doc set ships as v1.0.

The final milestone
easy - sessions 1-3 core - sessions 4-5 deeper - sessions 6-7 full stack - session 8 deep dives - anytime after session 5

Deep dives 🔬 · specialist topics · take anytime after Session 5

Four standalone specials for the docs that hurt most when they're bad - each one applied to Pulse's real errors, real alerts, and real style choices.

Choose your path 🗺️

Everyone starts at Session 1. The full journey ships Pulse v1.0; the fast-tracks fit a specific pain.

🚪 Ship a README this week 1→ 2→ 3→ 4
📟 The on-call engineer 1→ 5→ D3→ D1
✍️ Full practitioner journey 1→ 2→ 3→ 4→ 5→ 6→ 7→ 8→ deep dives

The knowledge map 🧠

The whole course at a glance - hover a session to spotlight its concepts, click any node to jump in.