Asked Gemini to create a baroque libretto to describe the current crisis. I wept a little.

English is my C++

Heard that Snowflake laid off its entire tech writing team. I can only say this: passo.uno/reconsider/

Troubleshooting an agentic workflow feels like robopsychology.

just saw my first `curl | claude` instead of `curl | bash` and you thought the arguments over piping to bash were contentious...

We're not at a point yet where things like skills crafting have become an art. We're far from it. I don't even know if it'll ever become a thing. Right now we're in the 10 PRINT 'HI' and 20 GOTO 10 stages of agentic expertise.

Hot take: A lot of software jobs are just creating weird ways to enter shit into a series of spreadsheets.

Without naming your job, tell me something you say over and over again at work. "No, a README is not enough. Of course you need proper docs."

I dabble in doodles.

one thing I do find exceedingly dumb about the MCP discourse is lamentations about token efficiency here's what's happened: everyone has built their MCPs like the fucking Chernobyl control room. this is a design decision being made, and people don't understand that they're making it

There’s an irresistible, almost demoralizing irony in the fact that developers are discovering docs and accessibility only now due to AI. They needed docs and didn’t know it until they had at their disposal an ersatz user in the form of an LLM that asked for context.

From the "Let's rediscover the wheel" department, today we've "Let's write docs in repos": www.dein.fr/posts/2026-0...

I dabble in doodles sometimes.

This is why we should've mandated the ELIZA vaccine years ago also there's vaccines from other manufacturers like drsbaitso that conferred immunity too

Pro tipo: Always write heartfelt thanks as if Sean Bean was to read them.

"Visibility can open doors, move you up career ladders, and help tip the scales in your favor the next time people start choosing who to keep and who to eject. Do what you enjoy — create content, and share it with people. Keep doing it." idratherbewriting.com/blog/crackin...

Now I only need to find out how to use the 387 gut coprocessors in my belly.

Skills are the greatest and most ironic tide turner for tech writers since LLMs arrived. Everybody's rediscovering docs.

Changed colors in my blog. It's more Windows 3.1 + IRIX now.

New Claude Code slash commands. Only post wrong answers. I'll start: /wtf Stop all subagents, apologize, and explain.

My feed is abuzz with people asking about linters and alternatives to Grammarly. 🐝.... Here are some open source options: - Harper: writewithharper.com - LanguageTool: languagetool.org - Vale: vale.sh If you know of others, feel free to share!

As the proverb says: "Give a dev an issue, and you'll get docs for a day; teach a dev to create skills, and you'll get tons of docs in advance"

The Elastic Docs Skills are open source now :) github.com/elastic/elas...

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 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...

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...

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

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

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.

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. :)

We need to cross posturing with docs. Docsturing.

"GPT 5.4 is out!" Me:

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.

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.

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

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.

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

Good docs require friction, tension, and truth. passo.uno/real-cost-of...

Inspired by one of @simonwillison.net 's reflections, I wrote a piece on the real cost of technical writing and documentation. passo.uno/real-cost-of...

Inspired by one of @simonwillison.net 's reflections, I wrote a piece on the real cost of technical writing and documentation. passo.uno/real-cost-of...

Every time I listen to Jean Michel Jarre's Equinoxe, I picture myself driving a Citroen CX over a laser grid with a panther on the backseat. Here, I asked Gemini to take a stab at it.

If you're not following @joanwestenberg.com here and elsewhere, you're missing out big time.

The “swarm of agents” model assumes work naturally splits into roles: marketing, sales, support, development = basically mirroring human job titles. But those titles and siloes are a byproduct of org scaling, not a universal truth about work. www.joanwestenberg.com/agentic-swa...

The worst thing about online learning is that everything has become a video. Every code tutorial. Every design tutorial. Nobody actually writes out a guide anymore. It's just "hey guys welcome to my tutorial" and watching 10 minutes of content that isn't remotely relevant...