Writing that earns
its place in the codebase
Stripe-Level API Reference
REST API documentation for a Series B fintech — 140 endpoints, zero ambiguity.
/v2/documents/{doc_id}/sectionsdocIdstringrequiredincludearraydepthintegerZero-to-Production in 20 Minutes
Developer onboarding guide for a cloud infrastructure platform. Churn on day one dropped 38%.
Installation
Before you install, confirm your environment meets the prerequisites on the previous page. A missing Node version is the most common source of friction here — the error message will tell you what it needs.
Run the initializer. It will ask three questions: your project name, your preferred package manager, and whether to scaffold example endpoints.
Documentation as Infrastructure
White paper commissioned by a compliance-heavy enterprise SaaS. Made auditors exhale.
"The compliance burden is not the regulation itself — it is the gap between what engineers build and what auditors can read."
Abstract
This paper examines documentation as infrastructure — not artifact. Organizations that treat their technical writing as a living system reduce mean time to onboard by 41% and cut tier-1 support volume by a third.
We present a framework for auditing existing documentation debt, prioritizing remediation by reader-impact score, and establishing continuous documentation practices within engineering sprints.
API Changelog — v3.2.0
Release notes written for the engineers who read them at 11pm before a deploy.
- Streaming response support for `/completions` endpoint
- Rate-limit headers now documented in all response schemas
- `cursor` pagination replaces `page` across all list endpoints — see migration guide
- `v1/` prefix endpoints sunset March 31, 2026
Craft, not
templates.
Every engagement follows a framework built from 200+ documentation projects. The process is consistent; the output is always specific to your system and your readers.
Start with a free audit→Documentation Audit
DiscoveryEvery engagement starts with a 48-hour audit of your existing docs. I map what exists, what readers actually need, and where the gaps create friction. You get a prioritized remediation list before any writing begins.
Information Architecture
ArchitectureStructure before prose. I diagram the reader's journey from "just arrived" to "successfully deployed" and design the navigation hierarchy around that path — not around how the engineering team thinks about the system.
Draft & Engineer Review
WritingFirst drafts go to your engineers for technical accuracy review. I've learned to write in a way that makes engineers comfortable marking up a document — specific questions, not vague edits.
Reader Testing
ValidationWhere possible, I test with actual developers — watching where they pause, where they search, where they give up. Documentation that doesn't survive a real onboarding session doesn't ship.