Live and recent posts from across the Fediverse tagged #technicalwriting, aggregated by home.social.
Tech Writer seeking work.
Based in BCN, open to remote.
• Reduced new writer onboarding from wks -> days on the RH Ceph Storage team.
• Reduced RH OpenShift ecosystem relnotes assembly time from 1 wk -> 2 days.
• Wrote initial docs @ Daytona, ToDesktop, Zephyr Cloud.
My background in SWE/CS means I rapidly understand new codebases & products.
Less back+forth -> quality docs, fast.
SWEs ❤️ working with me.
Boosts appreciated!
#GetFediHired #FediHire #Job #TechnicalWriting #WriteTheDocs
Two models, two jobs in my Claude Code setup.
I've tested Fable 5.2 since its release: very powerful for creative tasks and for reviewing work from a different angle, but probably too token hungry for all my workflows.
So Opus 5.5 does the work, and a Fable agent checks it, midway through a task or before my colleagues, the subject matter experts, review it.
Reviewing a training course after a product release? A Markdown diff is hard to read, so I asked Claude Code for a change page.
One command writes one HTML page:
- tracked changes word by word, or whole passages when rewritten
- before and after for screenshots and diagrams
- each change labeled by lesson, section or quiz question
- a Reviewed checkbox per file
I regenerate it after every edit, and the AI review agents check the same changes I do.
How do you network in 2026? I have found in-person events to be immensely helpful for staying up to date with industry trends, meeting new people, and strengthening existing relationships. #softwaredevelopment #technicalwriting #APIdocumentation
Your docs build passes, but are the pages still true? Treat documentation as views into a versioned product model, with Git and AI checking for drift. https://hackernoon.com/product-documentation-should-be-treated-like-a-data-model #technicalwriting
Ten years ago, this argument might have had some value.
About five years, after the launch of FreeCodeCamp, Udemy, DataCamp, etc. it started to loose relevance. With a little bit of effort, everyone who knew how use a computer and browse the Internet - including Technical Writers and Product Managers - could now learn how to use an API as a client and incorporate it in their own app.
Nowadays, after ChatGPT, after Claude Code, and after AI agents, I think this argument doesn't make any sense.
Since everyone can nowadays make use of a public API and include the services it provides in their own vibe-coding apps, what I think matters the most is for the author to explain pretty well what does an API endpoint serve for, what are its main use cases, and what edge cases, odd behaviors. or integration "gotchas" that the reader should be aware of. This last point is specially important if the reader is just an AI agent acting in the name of an end user.
Besides, we must always remember that API documentation is also part of Product Development. How can people start using your company's APIs if the documents doesn't highlight how people can and should integrate them on their apps/services?
So, yes: In my opinion this stance is totally outdated AND wrong.
"I don’t consider API documentation writing to be technical writing. I know many disagree. I assume they are saying this based on the similarities of the writing styles. It’s not the similarities that matter. It’s the differences.
API Documentation Has a Reliance on the Developer Experience
That doesn’t necessarily mean writing code examples or developing applications, although there is that aspect. It means thinking like a developer.
When a developer reads an API document, the first question is usually not what a parameter means in isolation. The developer wants to know how to use it to accomplish a task."
https://robertdelwood.medium.com/api-documentation-writing-is-not-technical-writing-f630d3778eba
#TechnicalWriting #APIs #APIDocumentation #SoftwareDocumentation #Programming