Posts
Thoughts on technical writing, documentation strategy, docs-as-code, and the evolving role of writers.
-
To those who fired or didn't hire tech writers because of AI
-
[Experiment] I interviewed Claude and Gemini about my 2025 blog posts
-
My day as an augmented technical writer in 2030
-
Code wikis are documentation theater as a service
-
You need an AI policy for your docs
-
Why I built an MCP server to check my docs (and what it taught me)
-
When docs become performance art, everybody loses
-
The future is open: Answering the most common tech writing worries
-
Contributing a verse: When users become documentation authors
-
AI must RTFM: Why technical writers are becoming context curators
-
How I write docs quickly
-
Things technical writers shouldn't care about... yet
-
Conjuring digital companions: How I'm thinking better through AI
-
On finding time to write (this is not productivity advice)
-
How to grow as a technical writer
-
Own the prompt: Build your own tech writing tools using LLMs
-
Update to my tech writing gear and tools
-
What's wrong with AI-generated docs
-
Technical writing has a depth issue
-
Technical English is nobody's mother tongue
-
My time machine runs on technical writing
-
Should you write documentation differently for LLMs?
-
The Seven-Action Documentation model
-
My technical writing predictions for 2025
-
The best docs are the ones we don’t remember
-
FAQs are not the answer
-
Why I became a Documentation Engineer (and what that even means)
-
How I'm using AI as a technical writer
-
What docs as code really means
-
TypeSpec reminds us why OpenAPI exists in the first place
-
Failing (and surviving failure) as a technical writer
-
How to set up your tech writer up for success
-
Contributing to open source docs as a technical writer
-
Review of Technical Writing for Software Developers
-
Technical writing is not a dead-end job, it's a landing pad
-
Things I remind myself when working with others
-
My favorite books for tech writers
-
The pros and cons of using Markdown
-
Technical writing in 2049
-
What to do when you're feeling AI anxiety as a tech writer
-
Signs that you need a technical writer
-
Docs observability, or measuring docs inside a product-docs system
-
What tech writers can learn from video game manuals
-
Tips for hiring your first technical writer
-
My favorite tech writing tools
-
Bestiary: On Doc Types and Other Animals
-
Tips for job hunting as a technical writer
-
An experiment in humorous documentation
-
A tech writer's letter to software developers
-
How did I become a technical writer
-
Docs-as-code topologies
-
We need more technical writing in popular culture
-
High fantasy map of technical writing
-
My technical writing gear (how I work)
-
Hiring technical writers in a ChatGPT world
-
The rise of WriterBot
-
How to become a technical writer
-
Learning to code as a technical writer
-
My first children’s book is about... OpenTelemetry
-
Circles of Product Truth
-
Docs Hierarchy of Priorities: A Proposal
-
Tech Writing Skills Tree
-
Measure it till you make it
-
A love letter to technical writing
-
Let's blog more about technical writing
-
How to introduce prose linters at your workplace
-
Do it yourself: User research for technical documentation
-
Markdoc is not what you expected, and that's a good thing
-
Technical writing syllabus
-
Why I collect and read old computer manuals
-
An update to my tips for working remotely
-
Better docs, less pain: the case for new docs-as-code standards
-
The Columbo Technique for Technical Writers
-
OpenAI and docs: AI-aided technical writing is here to stay
-
First steps with the Vale prose linter
-
Levels of embedded documentation
-
Working with remote teams: My Tips
-
What is technical writing?
-