I'm streaming KDE docs:

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

My shoulder and back are not great today, but I should be able to stream for one hour or two.

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 #Twitch

bnnuy cast

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

bnnuy cast

"If you are thinking about using an AI agent for documentation, here is what I think matters most.

Teach the agent, do not just instruct it. A prompt that says "write documentation for this feature" produces generic content. A skill that defines your voice, your formatting rules, your page structure, and your verification checklist produces documentation that sounds like your team wrote it. The upfront investment in the skill pays off on every subsequent page.

Make screenshots reproducible. Manual screenshots are the first thing that goes stale. A declarative manifest that can regenerate every screenshot in one command is worth the engineering effort. It changes screenshots from a one-time cost to a maintained artifact.

Phase your work. Even if you are using an agent, "write all the docs" is not a plan. Break it into phases with clear scope and clear deliverables. This gives you stopping points, review points, and the ability to course-correct.

Expect things to break. OCR will misread text. The UI will change mid-sprint. Preview URLs will go stale. The difference between a frustrating experience and a productive one is whether you encode the fix into a skill so it never happens again.

Review everything. The agent does not replace your judgment. It replaces the mechanical work. You still need to read every page, check every screenshot, and verify that the documentation matches what the user actually sees. The agent writes the first draft. You make it right."

https://dev.to/debs_obrien/how-i-documented-an-entire-product-in-4-days-with-an-ai-agent-3338

#TechnicalWriting #SoftwareDocumentation #AI #GenerativeAI #AIAgents #AgenticAI #LLMs

How I Documented an Entire Product in 4 Days with an AI Agent

I had 55 pages of documentation to write, 59 screenshots to capture, and a product that was still...

DEV Community

"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.

Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence β€” regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the β€œhelpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.

That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.

This is precisely why deterministic models and governance matter.

Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."

https://medium.com/@nc_mike/deterministic-and-agentic-ai-architectures-for-technical-documentation-3fb2956a1334

#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation

Deterministic and Agentic AI Architectures for Technical Documentation

Semantic Governance, Knowledge Graphs, Context Graphs, DOM Graph RAG, and Executable Validation for Enterprise Documentation Systems

Medium

The cost of not documenting software AKA why software companies will continue to need to hire and keep technical writers:

"Perhaps bizarrely, "the best documented game" in CD Projekt's history according to RuciΕ„ski is spin-off Witcher cardgame Gwent. "In a live service environment, which you could argue Gwent was, it is easy to say that you don't have the time to document everything, because the game is changing so fast," he said. "It receives patches, new content, new balance, every month. So all those documents need to be constantly updated, and somebody has to do that. It is a cost."

The developers opted to "pay this documentation tax upfront", however, rather than kick it down the road. As a result, said RuciΕ„ski, "new artists, new coders, new designers could jump onto any task within Gwent and contribute instantly." This demonstrates that "documentation doesn't have to slow you down, you don't have to think of documentation as something that will only be useful years later. Documentation can actually speed you up, make you faster right now."

Things didn't go nearly so well during the creation of Cyberpunk 2077 – a "true test of scale" for CD Projekt's technical writers. "Cyberpunk was a fresh start, but it came with new problems," Fulneczek recalled. "It was a massive undertaking. The hopes and expectations surrounding it were enormous. Internally, we had our documentation tool, Confluence, we had a proof of concept of 'living' documentation, so we thought, we were ready.

"But it turned out we weren't, because Cyberpunk was the first project of this scale, this size that we documented, and it also took a very long time," he went on. "And during those eight, nine years of development, we created over 8000 pages of documentation, and that's because of how complex this project was, and it also had many iterations along the way..."

https://www.rockpapershotgun.com/it-was-chaos-how-the-witcher-4-and-cyberpunk-2-are-learning-from-decades-of-cd-projekts-documentation-mistakes

#TechnicalWriting #SoftwareDocumentation #Documentation #Videogames #TechnicalCommunication

"It was chaos": How The Witcher 4 and Cyberpunk 2 are learning from decades of CD Projekt's documentation mistakes

CD Projekt are taking a new approach to internal documentation with The Witcher 4 and Cyberpunk 2, after major screw-ups during the creation of previous games.

Rock Paper Shotgun

I'm streaming KDE docs:

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

Today I'll continue working on updating plasmoid development docs.

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 #KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast #Twitch

bnnuy cast

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

bnnuy cast

Random plug for a documentation system I really enjoy and got to talk about with someone today.

If you struggle to write (or think about) good technical documentation like I do, you might benefit from learning about DiΓ‘taxis. https://diataxis.fr/

It breaks down the different reasons people go to learn and acquire information and it really helped me think about how I want to present information.

#diataxis #documentation #technicalwriting

'Good documentation is a tell-tale sign of a great product and a company that puts users first. There exist good products with bad or no documentation, but there are very few poor products with great documentation.'

--John Gruber, https://daringfireball.net/linked/2026/05/12/kagi-snaps

#TechnicalWriting #documentation

Kagi Snaps

Link to: https://help.kagi.com/kagi/features/snaps.html

Daring Fireball

I'm streaming KDE docs:

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

Today I'll continue working on updating plasmoid development docs.

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 #KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Owncast #Twitch

bnnuy cast

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

bnnuy cast