All blogs / Software / engineering practice
passo.uno
Technical writing, AI, and docs engineering by Fabrizio Ferri Benedetti.
- Posts
- 123 from 1 Jan 2001 to 29 Oct 2026
- Posting
- weekly (33 in the last year)
- Kind
- personal blog
- Feed
- https://passo.uno/index.xml
2026 28
- Rethinking the tech writing portfolio in the AI age
- Conventions used on this site
- Living House: Adaptive UI and docs using in-browser inference
- Episode XI of Phase One: Why docs still need an owner, with CT Smith
- Tech needs humanists more than ever
- Episode X of Phase One: Agent traffic, llms.txt, and the solitude problem
- Does whispering to agents in docs help?
- Episode IX of Phase One: Orchestrating docs, AI accuracy, and the pipeline writer
- Advice for tech writers on a job hunt in the AI age
- You can write in LLMese, but you don’t have to
- Feed the machines, then guide the humans
- Fine-tuning an LLM to write docs like it's 1995
- Episode VIII of Phase One: Judging beautiful docs, AI fatigue, and tool slop
- Behind the Docs: The Future of Docs Is More Human Than You Think
- What I've learned designing agentic workflows for docs
- Most vibe-coded tools are not for you
- What makes docs beautiful?
- Episode VII of Phase One: Skills, agentic workflows, and the tinker's burden
- High fantasy map of tech writing (AI edition)
- In the team of the future, roles are verbs, not nouns
- Episode VI of Phase One: Doc testing, skills files, and the guardians of knowledge
- Skills are docs, and docs need tech writers
- New habits for tech writers in the age of LLMs
- The writing was always the cheap part
- Episode V of Phase One: Tech comm predictions for 2026
- The four modes of AI-augmented technical writing
- To those who fired or didn't hire tech writers because of AI
- Episode IV of AI & Docs: AI tools, automation, and an intentionally offline life
2025 28
- My day as an augmented technical writer in 2030
- Episode III of AI & Docs: Docs theater and the acceleration paradox
- Code wikis are documentation theater as a service
- You need an AI policy for your docs
- Failing Well: A Practical Guide to Growth for Technical Writers
- Episode II of AI & Docs: MCP and the role of tech writers
- Why I built an MCP server to check my docs (and what it taught me)
- [Podcast] Growing as a technical writer in the AI era
- First episode of the AI & Docs podcast is out!
- 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
- Webinar: What's Wrong with AI Generated Docs
- 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)
- Beyond Content Types: A Human-first Model for Technical Documentation
- 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
2024 22
- My technical writing predictions for 2025
- The best docs are the ones we don’t remember
- FAQs are not the answer
- [Podcast] Your docs are your infrastructure
- 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
- Webinar: Contributing to Open Source Documentation Projects
- TypeSpec reminds us why OpenAPI exists in the first place
- Failing (and surviving failure) as a technical writer
- Discussing Markdown and structured content with Niklas Begley
- 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
2023 16
- What tech writers can learn from video game manuals
- Tips for hiring your first technical writer
- Chat with Tom Johnson about AI and tech comms
- My favorite tech writing tools
- Bestiary: On Doc Types and Other Animals
- Once Upon a Time There Were... Docs
- 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
- Episode 33 of API the Docs podcast
- 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
2022 16
- 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
- Episode 3 of Let's Talk Docs
- Why I collect and read old computer manuals
2021 9
- 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
- How to assist API design as a technical writer
- OpenAI and docs: AI-aided technical writing is here to stay
- Open source tools for REST API documentation
- On personality in technical writing
- First steps with the Vale prose linter
- Levels of embedded documentation