Blog
Insights & Guides
Tips on documentation, AI-powered workflows, and shipping better developer experiences.
Remote Teams Should Write Docs the Same Day They Decide
Most remote teams write docs as a summary of decisions made last week. By then the context is gone. Here's the decision-day docs rule I use instead.
Quickstart vs Tutorial: Which Should Your Docs Ship First?
Most SaaS startups ship a tutorial when they should have written a quickstart. Six dimensions, six verdicts, and a recommendation by use case.
Vercel Docs Teardown: Two Good Decisions, One Ongoing Mess
Vercel splits framework docs from platform docs. Smart. Next.js versioning across App Router and Pages Router is still a wreck. Teardown with specifics.
When to Hire a Technical Writer (It's Later Than You Think)
Most SaaS startups hire a technical writer six months too early. Here's the signal I actually watch for, and why the first docs hire is usually wrong.
Why Developers Don't Read Your Documentation
Developers don't read docs. They ctrl-F, scan for a code block, and bail in 90 seconds. Design for that, not for linear reading, and your docs stop failing.
API Reference Documentation: The Complete Guide (2026)
55% of developers cite documentation gaps as a top API blocker. Here's how great API reference documentation drives adoption and slashes support tickets.