<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The docs are alright</title><description>Rhys Vaughan, technical writer and documentation engineer. Portfolio, work, and a blog about documentation in a changing field.</description><link>https://rhysvaughan.dev/</link><atom:link href="https://rhysvaughan.dev/feed_rss_created.xml" rel="self" type="application/rss+xml" /><managingEditor>Rhys Vaughan</managingEditor><docs>https://github.com/rhys-vaughan/rhys-vaughan.github.io</docs><language>en</language><pubDate>Thu, 05 Nov 2026 16:18:30 +0000</pubDate><lastBuildDate>Thu, 05 Nov 2026 16:18:30 +0000</lastBuildDate><ttl>1440</ttl><generator>Zensical RSS</generator><item><title>The docs are alright</title><description>&lt;h1 id=&quot;the-docs-are-alright&quot;&gt;The docs are alright&lt;/h1&gt;
&lt;p&gt;Newer generations always have it tough. People say they&apos;re too lazy, too online, not trying hard enough. This kind of thing happens with every generation, yet somehow the kids keep turning out alright.&lt;/p&gt;
&lt;p&gt;I hear a version of this about software documentation now. AI will write all the docs. Nobody reads docs any more, they ask a chatbot. It&apos;s a bad time to be a technical writer.&lt;/p&gt;
&lt;p&gt;I don&apos;t agree. I&apos;ve only been a technical writer since 2021, and it&apos;s been a strange few years to start in, but I think it&apos;s an exciting time to be doing this job.&lt;/p&gt;
&lt;p&gt;At the start of this year my colleague left, and I became the only writer on our team. I decided it was the right time to move our help site from six MadCap Flare projects to a single &lt;a href=&quot;https://rhysvaughan.dev/work/docs-migration/&quot;&gt;docs-as-code site&lt;/a&gt;, and I got more done this year than I thought I could. That&apos;s because I could build my own tools: prose linting that knows our house style, checks that run every time I edit a page, and AI agents that review my changes before anyone else sees them.&lt;/p&gt;
&lt;p&gt;None of those tools wrote the docs. They handled a lot of the checking, so I could spend more of my time writing. An LLM can tell me a sentence breaks a rule, but it can&apos;t tell me whether a page answers the question a reader actually has, or whether a feature makes sense to someone who&apos;s never used it. It doesn&apos;t care what the docs mean. That&apos;s still my job, and I think it&apos;s an even more important one now.&lt;/p&gt;
&lt;p&gt;This blog is where I&apos;ll write about what I&apos;m learning as a technical writer while the job changes: the tools I&apos;m trying, what&apos;s worked, what hasn&apos;t, and where I still want a human in the loop.&lt;/p&gt;
&lt;p&gt;I think the docs are alright.&lt;/p&gt;</description><link>https://rhysvaughan.dev/blog/the-docs-are-alright/</link><source url="https://rhysvaughan.dev/feed_rss_created.xml">The docs are alright</source><pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://rhysvaughan.dev/blog/the-docs-are-alright/</guid></item></channel></rss>