I'm streaming KDE docs:

I'm streaming to both Owncast and Twitch right now.

Today I'll be focusing on the tutorial and API for KNotifications.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast #Rust #Twitch

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

I'm streaming KDE docs:

I'm streaming to both Owncast and Twitch right now.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast #Rust #Twitch

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

I'm streaming KDE docs:

I'm using Owncast where you can use emojis freely and join chat anonymously.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

Today I'll be retesting the KDE Rust bindings and merge the new docs letting you use KDE libraries from Rust.

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast #Rust

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

I'm streaming KDE docs:

I'm using Owncast where you can use emojis freely and join chat anonymously.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

"Can I convince AI to write useful content with minimal input from me? No. The input required is substantial; it's just a different kind of input than writing from scratch. Instead of staring at a blank page, I'm interrogating drafts, verifying claims, reframing angles, and restructuring articles. It's editing rather than writing, but it's not less work.

Can it provide a novel editorial take? Sometimes. The models produce serviceable takes that, with significant editorial shaping, become useful articles. But the novel connections, the thematic throughlines, the "this matters because of what we published last week" insights all come from me.

Can it produce accurate articles? Not without heavy verification. Every single article required factual corrections. Some were minor (wrong pipeline phase names, singular vs. plural). Some were serious (fabricated implementation details, wrong OWASP rankings, misleading CVE framing). The pipeline's verification step catches a small number of them. The rest require an editor who reads critically and clicks every link.

Can I edit out the AI writing tics? Mostly. The automated copy-editing pass handles the obvious markers. The subtler ones take manual work, and I'm still learning which tics I'm missing in my own editing passes.

I still think, for my needs, the pipeline is a useful tool for editorial content production. It's just not the "AI writes the blog" story that the stats at the top of this article might suggest. It's more like "AI produces a structured first draft that an experienced editor spends 90 minutes turning into something publishable." Whether that's worth it depends on what you value."

https://dacharycarey.com/2026/03/26/drafting-editorial-content-with-ai/

#AI #GenerativeAI #LLMs #TechnicalWriting #Writing #Blogging #Blogs

Drafting Editorial Content with AI | Dachary Carey

In which I use AI to help draft content, and discover its limitations.

I'm streaming KDE docs:

I'm using Owncast where you can use emojis freely and join chat anonymously.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

I'm streaming KDE docs:

I'm trying Owncast today; if it doesn't work well, I might fall back to Twitch.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

"With AI, the writer’s role moves to what I call context ownership. This is not a soft concept. A context owner is the person in your organization who governs what your AI tools know, how your content is structured, whether the output meets your quality and accuracy standards, and how your documentation systems connect to your product and engineering workflows.

In practice, context ownership looks like this:

A context owner defines and maintains the templates, standards, and structural rules that AI tools follow. Without these, AI produces content that is internally consistent within a single document but inconsistent across your documentation as a whole. Your customers notice, even if you don’t.

A context owner reviews and validates AI-generated drafts against product reality. AI tools do not know what your product actually does in edge cases. They do not know what changed in the last release that hasn’t been documented yet. They do not know that the API endpoint described in the engineering spec was modified during implementation. The context owner does.

A context owner manages the documentation pipeline. In a modern documentation operation, this means version control, docs-as-code workflows, API-driven publishing, and automated quality checks. These are technical systems that require technical management. AI can operate within these systems, but it cannot design, maintain, or troubleshoot them.

A context owner bridges engineering and customer-facing content. This is the function that has never been automated in any transition, and AI has not changed that. Someone has to understand what engineering built, determine what customers need to know about it, and make sure the documentation connects those two realities accurately.
(...)
This is not a diminished version of the writer’s role. It is a more senior, more technical role than “writer” has traditionally implied"
https://greenmtndocs.com/2026-03-25-ive-seen-this-before/
#AI #LLMs #TechnicalWriting #SoftwareDocumentation #ContextEngineering

I've Seen This Before: What Five Technology Transitions Tell Decision-Makers About AI and Documentation | Green Mountain Docs

The pattern is clear. The question is whether you'll repeat the expensive mistake.

Green Mountain Docs

I'm streaming KDE docs:

I'm trying Owncast today; if it doesn't work well, I might fall back to Twitch.

Be sure to join and ask any questions related to KDE and I'll try my best to answer them.

Every single stream I do is an Ask Me Anything KDE Edition ™️

#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast

Bnnuycast

I'm a hare pretending I'm a human pretending I know C++ and CMake 🐰

Bnnuycast

I've been testing #zensical since I will have to migrate off of #mkdocs and #mkdocsmaterial.

Across 3 sites, I only had to change one line in the yaml files and run `zensical` instead of `mkdocs`. Total potential migration time for 3 sites, 10 minutes.

Why potential and not complete? Pending blog and OpenAPI spec support. Once those are released, I can finish testing and migrate.

@squidfunk looking good so far. Thanks!

#technology #tech #indieweb #blog #technicalwriting #docs #docsascode