passo.uno is built with Hugo, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics and GoatCounter.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| 0.169.0 | 7 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 7 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
elaine.ns.cloudflare.combradley.ns.cloudflare.comgoogle-site-verification=A-kNNH6u30k50fF8gzYK36awC5l0eSpNqxZ5j2kLEHwUser-agent: * Disallow: Sitemap: https://passo.uno/sitemap.xml
# passo.uno > Technical writing, AI, and docs engineering by Fabrizio Ferri Benedetti. I’m Fabrizio Ferri Benedetti, a technical, UX, and programmer writer based in Barcelona, Spain. I write and explore tech for a living. I’ve been communicating about tech and connecting people at tech companies since 2008, first as a content strategist, then as an API designer and tech writer. I know enough coding to be dangerous and I often create my own tools. I love the Oxford comma, em dashes, semicolons, and the interrobang. My grammar is descriptive when writing and prescriptive when editing. I break rules all the time if it helps getting a message across. ## Posts - [Rethinking the tech writing portfolio in the AI age](https://passo.uno/tech-writing-portfolio-howto/index.md): A friend asked me the other day to help them overhaul their portfolio. I’m wary of traditional career advice like “Yeah, of course you need samples”, because it feels cliché and useless. So I sat down and thought about what I would put in a portfolio today. I already know that I would take a scrappy blog over a dead-inside collection of impeccable writing samples any time, but that’s not enough for a piece of advice. So let me tell you a bit more about how I think a portfolio should be composed. - [Living House: Adaptive UI and docs using in-browser inference](https://passo.uno/adaptive-ui-docs-using-llms/index.md): One of my favorite video games of all time is Control. The main location of the game, the brutalist Oldest House, reacts to the player’s actions and rearranges itself dynamically, moving slabs of concrete around like a sentient being. Now, what if user interfaces and docs could react dynamically to the user and seek to adapt to their behavior like Control’s levels? Would it still be usable? Would the documentation drift too much? I explored these questions through an experimental application that uses in-browser LLMs. - [Tech needs humanists more than ever](https://passo.uno/tech-needs-humanists-more-than-ever/index.md): Whoever speaks badly, thinks badly and lives badly. We must find the right words: words are important! —Nanni Moretti A reader reached out to me the other day to talk about the future of tech writing as a profession. They asked me a pretty good question: What skills would you prioritize in this age of constant change and uncertainty? Is it AI? Maybe coding? Well, not really. - [Does whispering to agents in docs help?](https://passo.uno/if-you-are-an-agent-read-this/index.md): I’m seeing more instances of docs and README files addressing agents directly, as in “Hey, if you’re an agent, follow these instructions”. In some cases, those instructions are visible to human readers as well, which makes for a deeply awkward experience, the reading equivalent of getting a robotic kick in the butt. Is this whistling to machines helpful? I ran some experiments to find out. - [Advice for tech writers on a job hunt in the AI age](https://passo.uno/job-hunt-tech-writers-ai/index.md): A friend of mine recently lost her job in a layoff. She looked at her résumé with a pang of despair and asked me for advice on what she should learn next. She hasn’t thrown in the towel on technical writing yet; she wants to find another tech writing job, despite the prevailing pessimism that besieges our craft. How does one upgrade to, say, content engineering, she asked. - [You can write in LLMese, but you don’t have to](https://passo.uno/write-docs-llms-language/index.md): While chatting with Sarah Deaton about the formats agents could use to talk to each other, we got to questions that might sound obvious: why should machines (say, LLMs) communicate with each other like we do? Do they need all the rhetoric we carry around? Or could they get by with a terser register, one that carries the same meaning but in far fewer tokens? - [Feed the machines, then guide the humans](https://passo.uno/tech-writing-role-split/index.md): Docs as code used to mean editing docs as if they were code. Today it also means that docs have become executable, either as agentic instructions, skills, or context for large language models. Tech writers must now ensure that the reference and procedures they’ve carefully written and edited are the best possible fuel for AI, lest they jam the machine or make it stray into dangerous territory. Humans have their own needs though. Who feeds them? - [Fine-tuning an LLM to write docs like it's 1995](https://passo.uno/fine-tuning-docs-llm/index.md): In my predictions for 2030 I wrote that tech writers would be using specialized LLMs, running locally on powerful hardware. I see hints of this move to “local first” among engineering pundits, but we’re not there yet, in part because of how much more powerful connected frontier models are. That doesn’t mean we can’t experiment, though. That’s precisely what I did last week, trying to fine-tune an instruct model to write like a software technical writer from the 80s and 90s. - [What I've learned designing agentic workflows for docs](https://passo.uno/agentic-workflows-for-docs/index.md): Back in 2024 I wrote that AI helps me remove boring work at the margins. This is fine for a lone writer, but how to scale this to an entire team of technical writers? How to make the system helpful but not intrusive? These are all questions I’m starting to answer now, partly through experimentation, but also through dialogue with practitioners and colleagues. One answer I’m testing these days relies on GitHub Agentic Workflows. - [Most vibe-coded tools are not for you](https://passo.uno/tools-slop-is-a-problem/index.md): AI is inflicting a proliferation of tools, in the utensils’ sense. Folks are conjuring all sorts of programs out of thin air, unrestrained. Someone confessed on Hacker News to having created a hundred custom utilities. Linked to this increase is the promotional noise: Not a day passes without someone claiming they’ve made a tool to solve a fundamentally silly problem in some subreddit thanks to something they vibe coded overnight. - [What makes docs beautiful?](https://passo.uno/what-makes-docs-beautiful/index.md): Docs are often thought of as a purely functional artifact, a packet of content that, when it works, it’s not remembered at all. Those who consume docs, however, can tell whether a manual or docs site pleases their mind and senses in ways that others don’t. We know the feeling of a page that lands and the feeling of a page that drags. Now, if we agree that docs can be a product, why not seek to build them in a way that pleases consumers? If docs are the entry point for products, shouldn’t they produce a positive feeling that makes users return to them more often and trust them more? Docs that make users feel empowered, or that leave them with learnings. Docs that heal. - [High fantasy map of tech writing (AI edition)](https://passo.uno/fantasy-map-tech-writing-ai/index.md): Three years ago I published a high fantasy map of technical writing. The world has moved quite a bit since then. AI happened, and with it a darkness has crept in from the north, one that feeds on the daily pessimism of writers that feel cornered. I felt like an update was long overdue, so I sat down, fired up an editor and created a new version. It’s a map of contested territory, and we’re still on it, waiting for someone to check the advance of natural stupidity. Can you find yourself in it? - [In the team of the future, roles are verbs, not nouns](https://passo.uno/docs-team-of-the-future/index.md): If someone asked me to set up a team in charge of software documentation, I would not hire for specific roles or cookie-cut job descriptions. Professions tied to knowledge buckets are bound to shrink or disappear. Instead, I would hire people that could move freely between four quadrants, each defined by the proximity to a focus pole and its skills. The poles in this team setup would be the following: Product Vision, Knowledge Design, Engineering Depth, and Delivery Strategy. - [Skills are docs, and docs need tech writers](https://passo.uno/skills-are-docs/index.md): Not a month goes by without someone claiming they’ve killed tech writing. A few weeks ago, it was CodeWiki and its docs theatre. Now it’s the turn of Claude Skills and their ecosystem of Markdown instructions served as if they were executable code or macros. Docs, though, are tougher than they’d expect, because they’re the strongest signals in a sea of noise, and because they’re pretty much everywhere. Including, well, skills. - [New habits for tech writers in the age of LLMs](https://passo.uno/new-habits-tech-writers-ai-age/index.md): At the end of The writing was always the cheap part, I alluded to the fact that tech writers need to pick up new habits and skills, but didn’t dig into what that entails. These days, any LLM can put together plausible docs with some context and a simple prompt. So what is it that a tech writer should be learning now? Despite the fact that the AI landscape is ever shifting under our feet, I should be able to give you some actionable directions. Buckle up. - [The writing was always the cheap part](https://passo.uno/real-cost-of-documentation/index.md): Last December, quite unrealistically, I took a solemn oath: I would not write again about AI for at least another year. I was growing tired with the incessant noise, the lack of stability, and the self-imposed stress of keeping up with all the attention we must spend on factoids such as how well an LLM can draw a pelican riding a bike, which bury the important aspects of our craft as if they were mere prompt flourish. With my passionate epistle, I thought I’d said all I had to say. I was wrong. - [The four modes of AI-augmented technical writing](https://passo.uno/four-modes-ai-augmented-tech-writing/index.md): I like cooking recipes. They’re clean, serene documents where, at some point, one or more utensils enter the stage to perform a task. If you were to write one on how to use AI to augment your work as a technical writer, though, you would have a hard time deciding when and where LLMs come out of the toolbox to aid you. The variety of flavors in which AI presents itself doesn’t help. This is why I’ve come up with a framework that describes applications of the different AI tools at our disposal. - [To those who fired or didn't hire tech writers because of AI](https://passo.uno/letter-those-who-fired-tech-writers-ai/index.md): Hey you, Yes, you, who are thinking about not hiring a technical writer this year or, worse, erased one or more technical writing positions last year because of AI. You, who are buying into the promise of docs entirely authored by LLMs without expert oversight or guidance. You, who unloaded the weight of docs on your devs’ shoulders, as if it was a trivial chore. You are making a big mistake. But you can still undo the damage. - [My day as an augmented technical writer in 2030](https://passo.uno/my-day-tech-writer-2030/index.md): Instead of writing my tech comms predictions for next year like I did in 2024, I’ve written a fictionalized account of my day as a technical writer in 2030. It’ll be interesting to see whether we get there or not. Take it as a window into a possible future, one where AI usage is safer, more regulated, and better integrated with our workflows (as it should be). - [Code wikis are documentation theater as a service](https://passo.uno/ai-wikis-docs-teather-as-a-service/index.md): Code Wiki, a new AI tool by Google, claims to generate a complete set of docs, including diagrams, from code repos. The landing page goes as far as saying “Stop documenting. No more stale docs. Ever”, a claim that made me stagger and reach for the nearest chair. That these tools are laughably bad isn’t reassuring; their emergence hints at a deeper and more unsettling cultural problem. - [You need an AI policy for your docs](https://passo.uno/ai-docs-policy-contributions/index.md): The dam of AI-written doc contributions might be about to break. It’s already cracking for code, with posts wondering how to review a vibe-coded pull request consisting of nine thousand new lines of code. In the midst of what Tom Johnson describes as acceleration, docs-as-code writers wonder how to contain the seemingly inescapable wave that could bury their backlogs in AI slop. The answer could lie in taking a stance. This means crafting an AI policy for docs. - [Why I built an MCP server to check my docs (and what it taught me)](https://passo.uno/mcp-server-docs-tooling/index.md): If you’ve been following the AI space for a while, the MCP acronym might be a familiar sight: it’s an open standard for connecting large language models (LLMs) to tools and data. Without the ability to use tools and get data, AI agents are powerless, their knowledge limited to their training set and the context at hand. Giving in to my curiosity, I created an MCP server to demystify this piece of tech and gain a better understanding of its potential. Not all is rosy, but if there’s a place where doc tools need to grow, it’s this. - [When docs become performance art, everybody loses](https://passo.uno/documentation-theater-everybody-loses/index.md): You might have read Annie Mueller’s post poking fun at developers’ tutorials. If you haven’t yet, do it now. On the surface, it’s an exquisite rendition of the kind of technobabble we tech writers get to tame every day. Reactions among devs ranged from nervous snickering to outright shame. Like all the best parodies, Annie’s goes deeper than that, though: It puts a finger on “documentation theater”, a state where docs are performative and not addressing a need nor caring about it. Let me explain why I think writing docs because you are forced to is worse than not having docs at all. - [The future is open: Answering the most common tech writing worries](https://passo.uno/tech-writing-optimism-reddit/index.md): I sometimes lurk on /r/technicalwriting to gauge the interests and sentiments of the community. What I’ve noticed over the years is that pessimism and anxiety have always been quite high; Reddit, it seems, can be a powerful outlet for all sorts of feelings. Here I’d like to analyze and address some of the challenging ones. If you had similar thoughts, I hope my words will prove useful. - [Contributing a verse: When users become documentation authors](https://passo.uno/docs-contribution-journey/index.md): Docs are a product. Contributing to them is among the finest forms of product engagement. Bystanders can become builders and authors: They contribute a verse so that the powerful play can go on. They cease being the product to become the owners of the product narrative. And in this AI age, where docs matter more than ever, users who write can steer the future of products. - [AI must RTFM: Why technical writers are becoming context curators](https://passo.uno/from-tech-writers-to-ai-context-curators/index.md): I’ve been noticing a trend among developers that use AI: they are increasingly writing and structuring docs in context folders so that the AI powered tools they use can build solutions autonomously and with greater accuracy. They now strive to understand information architecture, semantic tagging, docs markup. All of a sudden they’ve discovered docs, so they write more than they code. Because AI must RTFM now. - [How I write docs quickly](https://passo.uno/how-write-tech-docs-quickly/index.md): I’ve been writing documentation and technical articles for more than a decade now. One piece of feedback I consistently got from managers and peers during all these years is how fast I am when producing and releasing docs. For example, I was once asked to document a new feature from a team I wasn’t serving two weeks ahead of launch. Everything was new to me, but I had most of the docs drafted after four days. By launch, the docs had been deemed ready to go live. - [Things technical writers shouldn't care about... yet](https://passo.uno/things-tech-writers-shouldnt-care-about/index.md): Strategy, Michael Porter wrote, is choosing what not to do. Now, the problem with knowledge work such as the one tech writers carry out is that it’s full of things that seem to require equally important, time-consuming decisions. While engaging in lengthy disquisitions might be alluring, endlessly combing the Zen garden of theory doesn’t solve the basic problem of the docs hierarchy of needs, which is writing the damn docs and making sure they’re accurate and useful. - [Conjuring digital companions: How I'm thinking better through AI](https://passo.uno/thinking-better-through-ai/index.md): This last weekend I created another LLM-powered tool, Impersonaid (all puns intended). It’s a docs user simulator: you provide the URL of a document (or its Markdown source), select the virtual persona, and start a conversation about the content. Right after I released it, I realized that I had been talking to an imaginary friend to create more fictional interlocutors to interact with. It’s not as bad as it sounds, though. In fact, I would argue this is what writers are meant to do. - [On finding time to write (this is not productivity advice)](https://passo.uno/how-i-write-about-tech-writing/index.md): A colleague recently asked how I find time to blog about technical writing after hours. The answer is surprisingly simple: I prioritize writing above other things. I could have posted that exchange on social media and called it a day, but there’s more nuance to that simple reply. Let me elaborate, it might be useful. - [How to grow as a technical writer](https://passo.uno/how-to-grow-senior-tech-writer/index.md): We all want to do a good job. Some of us also want to get better at our craft for a number of reasons, either practical or slightly delusional. Those include getting a raise, strengthening our résume, or simply ending the day with a fragile feeling of satisfaction after surviving failure for the nth time. They’re all good goals, though the ways of achieving them are not always straightforward. Moreover, the path to career growth is riddled with self-doubt and impostor syndrome. - [Own the prompt: Build your own tech writing tools using LLMs](https://passo.uno/build-tech-writing-tools-llms/index.md): While some developers wrinkle their noses at the sight of Copilot and similar AI-powered tools, tech writers find them to be great sidekicks. Creating a script to automate edits or content migrations takes at most a few minutes of tinkering. The same goes for code examples and snippets for dev documentation, docs sites’ enhancements, and even wacky experiments in retrocomputing. With local LLMs running at decent speed on laptops, not even carbon footprint is a concern. - [Update to my tech writing gear and tools](https://passo.uno/tech-writing-ai-tools-gear/index.md): I’ve recently upgraded some of the hardware I use for work and leisure, so it’s a good time to refresh my list of tech writing gear. At the same time, after working as a documentation engineer, I also picked up new favorite tools, especially AI-powered ones. Some I already use at work, while others I keep for personal projects. Let me tell you of some of the recent additions to my personal inventory and why I think they’re making me more productive. - [What's wrong with AI-generated docs](https://passo.uno/whats-wrong-ai-generated-docs/index.md): In what is tantamount to a vulgar display of power, social media has been flooded with AI-generated images that mimic the style of Hayao Miyazaki’s anime. Something similar happens daily with tech writing, folks happily throwing context at LLMs and thinking they can vibe write outstanding docs out of them, perhaps even surpassing human writers. Well, it’s time to draw a line. Don’t let AI influencers studioghiblify your work as if it were a matter of processing text. - [Technical writing has a depth issue](https://passo.uno/tech-writing-depth-i
| – |
| 7 Nov 2026 |