// Topic

Technical Writing for DevTools

How to write documentation, tutorials, and developer content that engineers respect and buyers act on. The craft, the business case, and what separates practitioner writing from marketing.

Developers can smell marketing in one sentence and they close the tab. Content that earns their trust reads like it was written by someone who has shipped the thing, because it was. That is the whole game for DevTools content.

I came to writing from engineering, so the posts here treat docs as a product surface, not a chore. They cover the craft of writing for engineers, the business case that ties docs to revenue, and the patterns behind the teams who do it well.

Writing for engineers

The craft of content that a technical reader will actually trust.

Technical Writing for Engineers: The 80/20 Guide

Most engineering documentation fails for the same reasons. Here is what actually moves the needle.

12 min read technical-writing developer-experience engineering-culture

Technical Writing for AI Products: The New Rules

AI product docs now need prompts, schemas, evals, and version boundaries. I explain the rules I would use to judge a technical writer for an AI company.

12 min read technical-writing ai developer-experience

The Case for Shorter Technical Documentation

I think technical docs are often too long for the wrong reasons. Here’s why shorter docs usually work better, and where longer docs still earn their keep.

10 min read technical-writing documentation developer-experience

Specific formats

How to handle the documents developers read most.

Developer Onboarding Docs: What Works, What Doesn't

I’ve seen developer onboarding docs fail for the same reasons over and over. Here’s what actually helps a new engineer ship useful code in week one.

11 min read technical-writing developer-experience documentation

How to Write a Technical Tutorial That Actually Teaches

I explain how I structure technical tutorials so readers finish with a working result, fewer hidden assumptions, and less time wasted on broken examples.

13 min read technical-writing tutorials developer-experience

How to Write a Changelog That Developers Actually Read

Most changelogs exist to satisfy a checkbox. Here's what makes developers actually read them, and how to structure entries so breaking changes land before they cause incidents.

11 min read technical-writing developer-experience devtools

Writing Release Notes That Developers Trust

Developers trust release notes when they can make upgrade decisions fast. I explain the format, level of detail, and disclosure standard that earns that trust.

11 min read technical-writing developer-experience releases

The business case

Why docs move revenue, retention, and developer trust.

Why Devtools Startups Lose Deals Over Bad Docs

DevTools startups lose deals long before sales hears the objection. I explain how weak docs break evaluation, trials, and rollout confidence.

10 min read technical-writing devtools documentation

Technical Content as a Moat: the Long Game for Developer Tools

I explain why durable technical content compounds for developer tools, how strong docs and tutorials create distribution, and where teams usually waste the opportunity.

10 min read technical-writing developer-tools content-strategy

How Stripe's Technical Blog Became a Competitive Moat

I think Stripe’s technical blog compounds into a moat because it teaches, documents, and shapes developer trust long before a sales conversation starts.

10 min read technical-writing developer-marketing developer-experience

Quantifying the Engineering Velocity Impact of Technical Documentation

I analyze the structural correlation between documentation quality and engineering throughput, using DORA metrics and Accelerate research to quantify the ROI of technical writing.

10 min read engineering-velocity developer-productivity dora-metrics

Trust and craft

What makes practitioner writing outrank marketing, and how I got here.

The Developer Trust Hierarchy: Why Practitioner Writing Outranks Marketing Content

I analyze the structural reasons why engineers filter for technical depth and verify-ability, creating a 5-tier hierarchy of developer trust.

9 min read technical-writing developer-experience content-strategy

From Engineer to Technical Writer: What I Kept and What I Left Behind

I explain which engineering habits still make me better at technical writing, which ones I had to drop, and how the day-to-day work changed.

11 min read technical-writing career developer-experience

Frequently asked questions

What makes technical writing good for a developer audience?

Accuracy first, then a clear path to a working result. Engineers trust writing that shows real commands, real output, and the parts that usually go wrong. Marketing language and vague benefits make them leave.

Why do DevTools companies lose deals over bad docs?

Developers evaluate tools by reading the docs before they ever talk to sales. If the docs are thin or wrong, the evaluation stalls and the deal dies quietly. The lose-deals post breaks down where this happens.

How is writing for AI products different?

AI product docs have to cover prompts, schemas, evals, and version boundaries that change fast. The new-rules post covers the structure I would use to keep them accurate as the product moves.

Should technical docs be short or thorough?

As short as possible while still getting the reader to a working result. Length for its own sake hides the important parts. The shorter-docs post makes the case with examples.

Need a technical writer who gets this?

I write for DevTools and B2B SaaS companies. Let's talk.