<?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>Tue, 21 Apr 2026 10:33:01 GMT</pubDate>
    <lastBuildDate>Tue, 21 Apr 2026 10:33:01 GMT</lastBuildDate>
    <generator>Astro</generator>
      <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>
      <item>
        <title>Porting Jekyll to Astro with Claude Code</title>
        <description>This blog has been on Jekyll for a decade. Over that time I&apos;ve extended it with plugins and custom scripts, using liquid and Ruby, and hand-rolling it, prior to AI, locking me further into the ecosystem. I don&apos;t install Ruby or Jekyll and instead generate the site using docker containers, however recently those containers started throwing errors specifically in WSL on win11 (no problem on macOS or the linux-based GitHub runners). After failing a number of times to resolve my win11/WSL woes, I cracked it and began the port from Jekyll to Astro.</description>
        <pubDate>Sun, 21 Dec 2025 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2025/12/21/porting-jekyll-to-astro-with-claude-code/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2025/12/21/porting-jekyll-to-astro-with-claude-code/</guid>
        <category>ai</category>
        <category>astro</category>
        <category>claude-code</category>
        <category>jekyll</category>
      </item>
      <item>
        <title>Steering the Vibe: Verify</title>
        <description>This is the second post in a series about tightening the loop and improving the output when programming using AI code assist tools. In the previous post I introduced assist, the CLI I&apos;m building to enforce determinism on the LLM&apos;s output. In this post, we&apos;ll look at another command in the tool: assist verify</description>
        <pubDate>Sun, 14 Dec 2025 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2025/12/14/steering-the-vibe-verify/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2025/12/14/steering-the-vibe-verify/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
      <item>
        <title>Steering the Vibe: Commits</title>
        <description>This is the first post in a series in which I&apos;ll write about tightening the loop and improving the output when programming using ai code assist. This year has seen remarkable improvement in the capabilities of AI code assist tools but often this is missed by users who don&apos;t know how to get the best out of them. I hope to share some of my experiences and techniques in this series of posts as I too continue to learn ways to extract value from these emerging tools.</description>
        <pubDate>Sun, 07 Dec 2025 00:00:00 GMT</pubDate>
        <link>https://staffordwilliams.com/blog/2025/12/07/steering-the-vibe-commits/</link>
        <guid isPermaLink="true">https://staffordwilliams.com/blog/2025/12/07/steering-the-vibe-commits/</guid>
        <category>ai</category>
        <category>code-assist</category>
        <category>assist</category>
      </item>
  </channel>
</rss>
