<?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>AI on Daryl J. White</title>
    <link>https://djw.fyi/tags/ai/</link>
    <description>Recent content in AI on Daryl J. White</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://djw.fyi/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Interviewing in the age of AI</title>
      <link>https://djw.fyi/posts/2026/interviewing-age-of-ai/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/posts/2026/interviewing-age-of-ai/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/robot.jpg&#34;
         alt=&#34;A smile faced white robot with glowing eyes looks up towards a camera holding what looks to be a tablet.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@agk42/&#34;&gt;Alex Knight&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/high-angle-photo-of-robot-2599244/&#34;&gt;Pexels&lt;/a&gt;.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;I recently went through a round of interviews with several software companies in the cloud-native and developer tools space. While the tech stacks varied, one topic was ubiquitous: Generative AI.&lt;/p&gt;
&lt;p&gt;In 2026, simply saying, &amp;ldquo;I use AI to write faster,&amp;rdquo; isn&amp;rsquo;t enough. In fact, saying that might actually hurt your chances with companies that value security and original technical thought.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Documentation as the Knowledgeable Colleague</title>
      <link>https://djw.fyi/posts/knowledgeable-colleague/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://djw.fyi/posts/knowledgeable-colleague/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://djw.fyi/colleagues.jpg&#34;
         alt=&#34;Two women stand on opposite ends of a white board. One holds a marker while explaining a diagram to the other.&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@thisisengineering/&#34;&gt;ThisIsEngineering&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/photo-of-women-talking-beside-whiteboard-3861952/&#34;&gt;Pexels&lt;/a&gt;.&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;There&amp;rsquo;s a specific feeling you get when documentation actually works.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not relief, exactly.
It&amp;rsquo;s more like the feeling of asking a question and getting a straight answer from someone who knows what they&amp;rsquo;re talking about.
Someone who anticipated what you needed, skipped the parts you already knew, and told you what to do without talking down to you.&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>
  </channel>
</rss>
