Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #5543

F

Fabrizio Ferri Benedetti

Personal blog · passo.uno · on HN as theletterfwritingai

Fabrizio Ferri Benedetti's personal blog at passo.uno covers writing and ai. Since 2021, 14 different Hacker News readers have linked it 131 times, most often “The Seven-Action Documentation Model”. It is still writing: the last post was on 2026-10-29, and you can follow it by feed.

Visit the blog
131mentions?
14HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 48 in 2026

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

HN readers link Fabrizio Ferri Benedetti's technical writing posts on documentation models, docs-as-code architectures, and writing tooling such as Vale with Neovim.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Technical writing, AI, and docs engineering by Fabrizio Ferri Benedetti.

The author on HN?

theletterf · 2,435 karma · member since 2019

I'm a technical writer and aspiring developer based in Barcelona, Spain https://passo.uno

From their public HN profile, which links to this site.

Most-linked posts?

  1. The Seven-Action Documentation Model
    3 people · 5 mentions · first linked 2025-01-09
  2. What Makes Docs Beautiful?
    3 people · 4 mentions · first linked 2026-04-20
  3. FAQs Are Not the Answer
    3 people · 3 mentions · first linked 2024-12-01
  4. Fine-tuning an LLM to write docs like it's 1995
    3 people · 3 mentions · first linked 2026-06-01
  5. You can write in LLMese, but you don't have to
    2 people · 3 mentions · first linked 2026-07-12
  6. When docs become performance art, everybody loses
    2 people · 3 mentions · first linked 2025-09-24
  7. I collect and read old computer manuals
    2 people · 3 mentions · first linked 2022-02-16
  8. Tech Needs Humanists More
    2 people · 3 mentions · first linked 2026-09-07
  9. What's wrong with AI-generated docs
    2 people · 3 mentions · first linked 2025-04-01
  10. Why I became a Documentation Engineer (and what that even means)
    2 people · 2 mentions · first linked 2024-11-25

What Hacker News says?

  1. Docs... And a technical writer that'll tend to them. https://passo.uno/signs-need-tech-writer/

    Comment linking /signs-need-tech-writer/

    on “I've built my first successful side project, and I hate it”
  2. Submitted I collect and read old computer manuals as a story · 203 points

    HN discussion
  3. I do! https://passo.uno/best-tech-writing-books/

    Comment linking /best-tech-writing-books/

    on “Show HN: I spent 6 years building a ridiculous wooden pixel display”
  4. Submitted AI must RTFM: Why tech writers are becoming context curators as a story · 148 points

    HN discussion
  5. This is nice and fun for getting some fast indications on an unknown codebase, but, as others said here and elsewhere, it doesn't replace human-made documentation. https://passo.uno/whats-wrong-ai-generated-docs/

    Comment linking /whats-wrong-ai-generated-docs/

    on “Show HN: I built an AI that turns GitHub codebases into easy tutorials”
  6. Submitted What docs-as-code means as a story · 102 points

    HN discussion
  7. The best docs are the ones that satisfy user needs. https://passo.uno/seven-action-model/

    Comment linking /seven-action-model/

    on “Examples are the best documentation”
  8. Submitted The Seven-Action Documentation Model as a story · 96 points

    HN discussion
  9. Besides emojis, I find it too long. READMEs should be succinct and be like a switchboard to other docs (much like LLMS.txt tries to be for agents). Also, it features an FAQ. FAQs are problematic (as in not often effective): https://passo.uno/what-the-faq/ Edit: Clarification

    Comment linking /what-the-faq/

    on “I paid people to try and follow my README”
  10. Submitted Tech Needs Humanists More as a story · 86 points

    HN discussion
  11. This means jokes and humour in technical documentation. While it's often frowned upon, I love a bit of humour in docs. I wrote about this here: https://passo.uno/experiment-humour-documentation/

    Comment linking /experiment-humour-documentation/

    on “Jokes and Humour in the Public Android API”
  12. Submitted Code wikis are documentation theater as a service as a story · 41 points

    HN discussion
  13. It's in their about page. https://passo.uno/about/

    Comment linking /about/

    on “Writing like a pro with Vale and Neovim”
  14. Submitted How to Grow as a Technical Writer as a story · 11 points

    HN discussion
  15. As a technical writer, I use Vale every day. It helps protect consistency and style. I wrote a brief tutorial here: https://passo.uno/posts/first-steps-with-the-vale-prose-lint...

    Comment linking /posts/first-steps-with-the-vale-prose-linter/

    on “Writing like a pro with Vale and Neovim”
  16. Submitted When docs become performance art, everybody loses as a story · 9 points

    HN discussion
  17. Don't fall into the trap of the new SEO for AIs. LLM are just like users. https://passo.uno/writing-for-llms-ai-chatbots/

    Comment linking /writing-for-llms-ai-chatbots/

    on “Writing documentation for AI: best practices”
  18. Submitted Tech needs humanists more than ever as a story · 6 points

    HN discussion
  19. You need great pre-existing docs for something like this to work properly. AI must RTFM. https://passo.uno/from-tech-writers-to-ai-context-curators/

    Comment linking /from-tech-writers-to-ai-context-curators/

    on “AI documentation you can talk to, for every repo”
  20. Submitted Update to my tech writing gear and tools as a story · 5 points

    HN discussion
  21. Author here. No, I don't think it does. https://passo.uno/ai-anxiety-tech-writer-howto/

    Comment linking /ai-anxiety-tech-writer-howto/

    on “What docs-as-code means”
  22. Submitted Contributing to open source docs as a technical writer as a story · 5 points

    HN discussion
  23. I love old manuals. I partially answered that question here: https://passo.uno/why-collect-read-old-computer-manuals/

    Comment linking /why-collect-read-old-computer-manuals/

    on “Manx – a catalog of manuals for old computers”
  24. Submitted Advice for tech writers on a job hunt in the AI age as a story · 4 points

    HN discussion
  25. Technical writing is one of those jobs where it's tempting to think that AI will indeed take humans' jobs. But only a company that has gone bananas would do that. All it takes is understanding that the deliverable is not the job; there's so much more to it. I wrote about it here for my fellow writers: https://passo.uno/ai-anxiety-tech-writer-howto/

    Comment linking /ai-anxiety-tech-writer-howto/

    on “The idea that AI will just augment jobs never replace them”
  26. Submitted Show HN: I remade my blog into a Windows 3.1 environment as a story · 4 points

    HN discussion
  27. Video games used to have user manuals. Some were great and memorable! https://passo.uno/video-game-manuals-docs/

    Comment linking /video-game-manuals-docs/

    on “The quest for a Wiki-less game”
  28. Submitted My day as an augmented technical writer in 2030 as a story · 4 points

    HN discussion
  29. Technical writing will be safe, but only if writers embrace computer-aided writing. https://passo.uno/posts/computer-aided-technical-writing-is-...

    Comment linking /posts/computer-aided-technical-writing-is-here-to-stay/

    on “Ask HN: What creative field will be safe from AI?”
  30. Submitted Technical writing has a depth issue as a story · 4 points

    HN discussion

Search all of HN for passo.uno

Linked by the same people?