passo.uno

Prose linters are great at checking documentation against style guides, either in code editors or when running a CI/CD pipeline.

As a technical writer, I often want to know what works and what doesn’t in the docs I’ve released.

Beholding Stripe’s excellent documentation and wondering how they’ve built it is a modern technical writing trope.

A few months ago, I drafted a technical writing syllabus.

Episode 3 of the Let’s Talk Docs podcast is out, hosted by Portia Burton and Eric Holscher (founder of Read the Docs and Write the Docs).

It’s my ritual: every time I enter a secondhand bookshop, I go straight to the Sciences section and search for old computer manuals.

Almost two years passed since I published my tips for working remotely.

Despite the massive growth of docs-as-code as a documentation ethos, I continue to be surprised, year after year, by the lack of robust docs-as-code tools.

A colleague asked me the other day what’s my favourite way of extracting information from subject-matter experts (SMEs).

The programmatic equivalent of UX Writing is API Design.

I get it.

A hands-on review of the most recent open source API documentation toolchains, such as ReDoc, Widdershins, and Elements, the newest solutions from Stoplight, among others.

Had this lovely chat with Chris Ward and Tom Johnson on personality and authorship in technical documentation for the Write the Docs Podcast.

Code linters support developers by catching errors and stylistic issues in code, such as bad formatting or keywords in the wrong places.

There was this discussion at work regarding docs in products, so I sketched a diagram to illustrate the main types of embedded docs, and their place in the product writing continuum, from UX writing to technical writing.

I’ve been working with remote teams for years.

From time to time, people ask me about technical writing and the type of work I do.

I’m Fabrizio Ferri Benedetti, a technical, UX, and programmer writer based in Barcelona, Spain.