<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>stafford williams</title>
    <description>software by Stafford Williams</description>
    <link>https://staffordwilliams.com/</link>
    <atom:link href="https://staffordwilliams.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Sat, 03 Oct 2026 01:33:38 GMT</pubDate>
    <lastBuildDate>Sat, 03 Oct 2026 01:33:38 GMT</lastBuildDate>
    <generator>Astro</generator>
      <item>
        <title>Steering the Vibe: Worktrees</title>
        <description>After failing a number of times to implement worktrees, I got over my frustration and made it happen. The result was a huge productivity multiplier, though not without solving some tricky problems. In this post I&apos;ll share both how I solved the problem of continuously failing, and how I ended up implementing worktrees.</description>
        <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/09/15/steering-the-vibe-worktrees/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/09/15/steering-the-vibe-worktrees/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>How I Build Software in June 2026</title>
        <description>The pace of AI improvement has meant the way I build software looks very different to how I did six months ago, and again six months before that. The change over time is now so constant that it&apos;s difficult to explain to others what the tools are and what my current approach is without sounding like the charlie-day.gif. In this post I hope to explain to you, and myself, what my approach to building software is right now.</description>
        <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/06/28/how-i-build-software/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/06/28/how-i-build-software/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Steering the Vibe: Orchestration</title>
        <description>Earlier this year I spoke to the idea of Agent Orchestration where changes to software span multiple context windows, and work needs to be split and passed to agents while monitoring progress deterministically</description>
        <pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/04/30/steering-the-vibe-orchestration/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/04/30/steering-the-vibe-orchestration/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Steering the Vibe: Permissions</title>
        <description>Once your agentic code-assist workflow is consistently producing acceptable code the bottleneck to productivity becomes the speed at which you can produce this code. One of the biggest slowdowns is when the tool prompts you - usually for permission to perform some task, and even just a few questions from the tool can severely cap sessions running in parallel. In this post we&apos;ll look at refining Claude Code&apos;s permissioning approach to reduce the number of questions asked and speed up the workflow.</description>
        <pubDate>Sun, 08 Mar 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/03/08/steering-the-vibe-permissions/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/03/08/steering-the-vibe-permissions/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Steering the Vibe: Complexity</title>
        <description>In this post I&apos;ll describe an improved method to guide the output of code-assist tools towards more maintainable code. In a previous post, I described a refactor approach where periodically I would command the tool to break down files into smaller modules. However knowing (or remembering) when to run it, and having it based on some arbitrary line count was not ideal. That earlier approach has now been superseded by a complexity-based approach that runs as a part of the normal verify workflow.</description>
        <pubDate>Sun, 22 Feb 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/02/22/steering-the-vibe-complexity/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/02/22/steering-the-vibe-complexity/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Steering the Vibe: Review</title>
        <description>This is the fourth post in a series about steering AI code assist (code-assist) towards producing maintainable code. This particular post will look at a workflow outside the core loop of generating code and gives insight into how the tools we&apos;re already using can be leveraged to improve more than just writing code. Specifically this post will explore improved pull request (PR) processes.</description>
        <pubDate>Wed, 11 Feb 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/02/11/steering-the-vibe-review/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/02/11/steering-the-vibe-review/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Quality and Suffering in Software Delivery</title>
        <description>The way I deliver software is grounded in a belief that quality matters and is the route to less suffering. After building software for a long time my approach has become tacit knowledge - helpful in work I&apos;m directly involved with but elusive to others, and more recently, AI. I need to write it down but I&apos;ve been extremely good at allowing the annoying complexity to keep me procrastinating. For every guideline I have, I can think of exceptions and a context where it doesn&apos;t apply. But the efficiency of having it written down is now higher than ever - not only can it help me clarify my thinking, and you to understand my approach, but I can use it to build or evaluate AI tooling to help teams deliver software better and faster than ever before.</description>
        <pubDate>Sun, 01 Feb 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/02/01/quality-and-suffering/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/02/01/quality-and-suffering/</guid>
        <category>software-delivery</category>
        <category>ways-of-working</category>
        <category>quality</category>
      </item>
      <item>
        <title>Agent orchestration</title>
        <description>So the agent and I determined what it needed to do and it built a plan and the plan was split into multiple steps with the intention of progressing one step at a time with the reasoning being I want to use as little of the context window as possible for each step so quality remains high. I had a progress file and it would check off each step as it was done, and I&apos;d clear the context window between steps. This approach revealed some problems:</description>
        <pubDate>Thu, 15 Jan 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/01/15/agent-orchestration/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/01/15/agent-orchestration/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>agent-orchestration</category>
      </item>
      <item>
        <title>Twelve months of agentic AI code-assist</title>
        <description>2025 was the year of agentic AI code assistants and programming will never be the same. For some, these tools have become a critical part of their daily workflow and produce most, if not all, of the code they write. For others, these tools remain experimental and unreliable, producing more frustration than value.</description>
        <pubDate>Sun, 04 Jan 2026 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2026/01/04/twelve-months-of-agentic/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2026/01/04/twelve-months-of-agentic/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>claude-code</category>
      </item>
      <item>
        <title>Steering the Vibe: Refactor</title>
        <description>This is the third post in a series about steering AI code assist (code-assist) towards producing maintainable code. In this post I&apos;ll discuss the refactor commands I&apos;ve added to assist, the CLI tool I&apos;m building to share deterministic patterns across code-assist workflows.</description>
        <pubDate>Mon, 29 Dec 2025 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2025/12/29/steering-the-vibe-refactor/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2025/12/29/steering-the-vibe-refactor/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
  </channel>
</rss>
