Fabrizio Ferri-Benedetti

Big updates to the @elastic.co Lens documentation! 📊

The team has added great technical tips, including:
• Metric trends: www.elastic.co/docs/explore...
• Reference lines: www.elastic.co/docs/explore...

Read more: www.elastic.co/docs/explore...

🙏🏼✨

Astro 6.0 | Astro Astro 6 is here with a refactored dev server, an experimental Rust compiler, live content collections, CSP, and more.

Astro 6 is here! We completely rebuilt the Astro dev server and build pipeline onto a new, more powerful runtime-agnostic architecture.

Plus: New Fonts API, CSP support, an experimental new Rust compiler, and more...

astro.build/blog/astro-6...

Episode VI of Phase One: Doc testing, skills files, and the guardians of knowledge Sixth episode of the AI & Docs podcast series is up! In this one, Tom, Manny Silva, and I talk about documentation testing (the deterministic kind), skills files and why they matter, the ethical tensi...

Where I introduce the "Guardians of knowlege" role:

"Picture the librarians of old, guarding the knowledge and taking care of the old tomes. We really need machines not to touch that. We need that high-quality signal, and extract it and use it when necessary."

passo.uno/episode-vi-p...

Slack

From an engineering community's Slack. That's an engineer wondering. I giggled.

Skills are docs, and docs need tech writers 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 inst...

Tech writers must co-own skills as a new channel for documentation: passo.uno/skills-are-d...

a man wearing a sheriff 's uniform is reading a newspaper ALT: a man wearing a sheriff 's uniform is reading a newspaper

Me when I read that post:

Wrote about it: bsky.app/profile/thel...

Skills are docs, and docs need tech writers 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 inst...

Tech writers must co-own skills as a new channel for documentation: passo.uno/skills-are-d...

Sigh. Skills are docs. They literally are docs. If you let them AI produce them, you're essentially letting entropy in by giving up on high-signal content made by humans who *know* what the things are about.

Pretty good :)

We need to go touch some grass.

I've discovered that lots of non-writers in tech suck at creating documentation using LLMs. They just don't know what to ask, how to ask it, what good looks like, what context they should use, and so on. Allow me this unglorious bit of schadenfreude.

Fed 8 hours of AI office hours' transcripts to Cursor to create internal documentation for AI tooling for the team. Talk about brute-force. :)

RFC: Request for Claptrap.

We need to cross posturing with docs.

Docsturing.

a man says oh come on man in a dark room ALT: a man says oh come on man in a dark room

"GPT 5.4 is out!"
Me:

Neuromancer

Using OpenClaw is quite close to summoning Dixie Flatline. That's probably why I chose to call my OpenClaw "Dixie". (Not sure if @greatdismal.bsky.social would approve, though.)

This is human earned context in an academic setting. 😆

This is why I like Git version control & ‘git blame’ for understanding the writing/drafting process.

Me too...

I explained to my wife, who is a doctor, what our role looks like in this AI transformation thus. She panicked, so I think she understood.

Imagine that software developers create a nurse robot that knows how to provide drugs only based on its model knowledge, which might be outdated, wrong, hallucinated, or based on the wrong criteria. We writers are the doctors and need to speak up so that the robot doesn’t harm patients.

The AI tooling scene is more thrilling than watching a K-drama series.

The very definition of frolicking.

Yummi

Closed my Mastodon account for various reasons. I'll focus on this one from now on.

I'm afraid the only way to get them to change their ways is by creating skills that work better than theirs, based on docs principles.

New habits for tech writers in the age of LLMs 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 t...

Wrote something based on what I'm currently doing and promoting at work. Strong overlap with @tomjoht.bsky.social and Dachary Carey's recent posts, which I take as a good sign. passo.uno/new-habits-t...

Feeling slightly upset as I see developers coming up with Agentic "helpers" fed by docs whose provenance, quality, and maintenance is unknown, eager to just use context as some sort of agentic boilerplate.

If you waaaant!

Docs cartridge

This is one of the possible futures of technical documentation. In some ways, it's already the present.