<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docs-as-Code on Daryl J. White</title>
    <link>https://djw.fyi/tags/docs-as-code/</link>
    <description>Recent content in Docs-as-Code on Daryl J. White</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://djw.fyi/tags/docs-as-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Setting up for a successful first week</title>
      <link>https://djw.fyi/posts/2026/successful-first-week/</link>
      <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/posts/2026/successful-first-week/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;How I’m engineering a successful first week in my new docs role.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/clear-desk.jpg&#34;
         alt=&#34;A gray office desk, freshly cleaned, sporting a keyboard and trackball, laptop on a stand, monitor, water ball, desk lamp, cup of pens, new legal pad with a pencil, and a LEGO Rivendell.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;My desk, newly cleaned and ready for new things.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;The gap between signing a job offer and your official start date is a unique kind of limbo.
The &amp;ldquo;open source&amp;rdquo; part of my brain wanted to start coding (or in my case, PRing docs) immediately.
My previous post, though, was about the strategic necessity of a total mental disconnect.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Avoiding the Silent Stale Doc Problem</title>
      <link>https://djw.fyi/portfolio/preventing-drift/</link>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/portfolio/preventing-drift/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/car-snow-drift.jpg&#34;
         alt=&#34;A mustard yellow car drifts across the snow along a track with spectators watching from beyond a chainlink fence.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@asemirski/&#34;&gt;Aliaksei Semirski&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/a-car-drifting-on-snow-covered-road-14667974/&#34;&gt;Pexels&lt;/a&gt;.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;We’ve all been there.
The team is firing on all cylinders, cranking out innovative new features.
The documentation is perfect!
It&amp;rsquo;s comprehensive, clear, and included right in the Pull Request.
Then, six months later, a bug report comes in.
Somewhere along the way, a developer changed a timeout value, renamed a key in a JSON response, or updated a UI label, and&amp;hellip;the documentation didn&amp;rsquo;t move an inch.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How I Integrated Claude Into a Documentation Workflow — and What It Actually Changed</title>
      <link>https://djw.fyi/portfolio/integrating-ai/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/portfolio/integrating-ai/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/helping-hand.jpg&#34;
         alt=&#34;Close up photo of a hand stretched out with palm facing up in a gesture of assistance or help.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@pixabay/&#34;&gt;Pixabay&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/close-up-of-hand-over-white-background-255527/&#34;&gt;Pexels&lt;/a&gt;.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;AI tools are everywhere in documentation conversations right now, but most of the discussion stays abstract.
This is a concrete account of how I integrated Claude into MinIO&amp;rsquo;s documentation workflow:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;what I used it for.&lt;/li&gt;
&lt;li&gt;how I structured that use.&lt;/li&gt;
&lt;li&gt;what it measurably changed about how the team worked.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&#34;the-starting-point&#34;&gt;The Starting Point&lt;/h2&gt;
&lt;p&gt;Technical documentation for a product like MinIO lives close to the codebase.
Keeping it accurate means tracking software releases, triaging GitHub issues, auditing existing content, and staying current with a fast-moving engineering team.
All while writing new content and updating existing content.
The surface area is large and the feedback loops are long.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Spokes of the Wheel</title>
      <link>https://djw.fyi/posts/spokes/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/posts/spokes/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/bicycle-wheel.jpg&#34;
         alt=&#34;Close up photo of the wheel of a light blue and white bicycle showing the psokes coming off the hub and the bicycle chain. The bicycle sits in the grass next to a blurred gravel trail.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@adam-dubec-745977/&#34;&gt;Adam Dubec&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/close-up-photo-of-bicycle-chain-1595485/&#34;&gt;Pexels&lt;/a&gt;.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;If you look at a standard corporate org chart, you’ll see neat little boxes.
Engineering is over here, Product is over there, Sales is on the other side of the building (or the virtual workspace), and Support is tucked away in the corner.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Engineering the &#34;Golden Path&#34;</title>
      <link>https://djw.fyi/portfolio/golden-path/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/portfolio/golden-path/</guid>
      <description>&lt;h2 id=&#34;modernizing-documentation-at-cloud-scale&#34;&gt;Modernizing Documentation at Cloud Scale&lt;/h2&gt;
&lt;p&gt;In the world of high-performance distributed systems, documentation is more than just a manual.
Instead, the docs serve as a critical component of the user’s infrastructure.
During my tenure as a Senior Technical Writer at MinIO, I transitioned from being a content creator to a &amp;ldquo;Documentation Architect.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;My GitHub contributions reflect the level of work:&lt;/p&gt;
&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/djw-2026-GitHub.png&#34;
         alt=&#34;GitHub metric contributions for my profile, djwfyi, showing 839 contributions during the previous year from March 2025 through March 2026. 22% to conde reviews, 31% to commits, 20% to issues, and 27% to pull requests across two MinIO organizations and the Write the Docs repository.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;My GitHub metric contributions for the year leading up to February 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
