<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI on jeffcarp</title>
    <link>/categories/ai/</link>
    <description>Recent content in AI on jeffcarp</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/categories/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using AI in a Slower Way Increased the Quality of my Work</title>
      <link>/posts/2026/new-ai-workflow/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026/new-ai-workflow/</guid>
      <description>&lt;p&gt;I think the way most people use coding agents is to 1. prompt the agent, 2. review its output, then&#xA;repeat the cycle from there until a suitable finished product is created.&lt;/p&gt;&#xA;&lt;p&gt;Working this way, I&amp;rsquo;ve frequently gotten stuck in the common trap of not having the full context on what the agent did,&#xA;unless I take the time to fully review everything the agent did and internalize it.&#xA;The longer this loop continues, the less context I have about how my codebase works as a whole.&#xA;Of course it&amp;rsquo;s possible to ask the agent questions to understand newly generated code better,&#xA;but at that point I&amp;rsquo;ve lost most of my mental model for the codebase and am effectively doing&#xA;archaeology on my own project.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
