<?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>LLMs on Daryl J. White</title>
    <link>https://djw.fyi/tags/llms/</link>
    <description>Recent content in LLMs 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/llms/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>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>
  </channel>
</rss>
