<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gears Within Gears</title><link>https://brianguthrie.com/categories/ai/</link><description>Gears Within Gears</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 14:30:12 +0000</lastBuildDate><atom:link href="https://brianguthrie.com/categories/ai/" rel="self" type="application/rss+xml"/><item><title>Introducing Prospero: Superpowers for writing</title><link>https://brianguthrie.com/p/prospero/</link><pubDate>Thu, 30 Apr 2026 10:00:00 -0400</pubDate><guid>https://brianguthrie.com/p/prospero/</guid><description>&lt;blockquote&gt;
&lt;p&gt;No man but a blockhead ever wrote, except for money.
— Samuel Johnson&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I like the act of &lt;em&gt;writing&lt;/em&gt;, but often find actually &lt;em&gt;publishing&lt;/em&gt; paralyzing. I&amp;rsquo;ll sit with a piece for weeks, hem and haw over it and chew on it and maybe pass a draft around, but by the time I&amp;rsquo;m done I&amp;rsquo;ll have lost whatever conviction I started with. A fair number of pieces never finish, and the drafts folder keeps growing. Consequently, I tend to think of myself as a better editor than an author; responding to a piece is less taxing than authoring one.&lt;/p&gt;</description></item><item><title>Software architecture after AI</title><link>https://brianguthrie.com/p/software-architecture-after-ai/</link><pubDate>Tue, 21 Apr 2026 06:00:00 -0500</pubDate><guid>https://brianguthrie.com/p/software-architecture-after-ai/</guid><description>&lt;p&gt;One of the more useful definitions of software architecture comes from &lt;a href="https://evolutionaryarchitecture.com/"&gt;Building Evolutionary Architectures&lt;/a&gt;: architecture is definitionally the stuff that&amp;rsquo;s hard to change.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; I&amp;rsquo;ve always found this definition to be the most honest framing available, to say nothing of the simplest. It doesn&amp;rsquo;t pretend architecture is about beauty or correctness or your resident architect&amp;rsquo;s favorite stalking-horse. It acknowledges that what makes a decision &amp;ldquo;architectural&amp;rdquo; is not its conceptual weight but its &lt;em&gt;cost to reverse&lt;/em&gt; and its &lt;em&gt;business impact&lt;/em&gt;. And &amp;ldquo;hard to change&amp;rdquo; has always been, at root, about wall-clock time: coordination cost, incident mitigation, cognitive load, handoff friction. Software architecture has always been a labor problem dressed up as a design problem.&lt;/p&gt;</description></item><item><title>AI isn't a value-add for software; software is a value-add for AI</title><link>https://brianguthrie.com/p/ai-isnt-a-value-add-for-software-software-is-a-value-add-for-ai/</link><pubDate>Sat, 14 Mar 2026 10:00:00 -0400</pubDate><guid>https://brianguthrie.com/p/ai-isnt-a-value-add-for-software-software-is-a-value-add-for-ai/</guid><description>&lt;p&gt;When a company hits a ceiling on its core business, it often tries to grow demand. The Michelin Guide wasn&amp;rsquo;t about restaurants; it was about miles driven. Facebook&amp;rsquo;s &lt;a href="https://about.fb.com/news/2013/08/technology-leaders-launch-partnership-to-make-internet-access-available-to-all/"&gt;internet.org&lt;/a&gt; wasn&amp;rsquo;t about altruism; it unlocked expansion by growing the size of the entire internet. The ceiling on the business was the medium, so they expanded it.&lt;/p&gt;
&lt;p&gt;AI companies face the same structural problem: their constraint on inference revenue is the volume of tasks that flow through models. From where they sit, &lt;em&gt;every piece of software that still runs without model calls is unrealized market&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Accumulated ignorance at scale</title><link>https://brianguthrie.com/p/accumulated-ignorance-at-scale/</link><pubDate>Fri, 06 Mar 2026 12:00:00 -0500</pubDate><guid>https://brianguthrie.com/p/accumulated-ignorance-at-scale/</guid><description>&lt;p&gt;We have entered a period in which AI is able to author more code than is reviewable by humans. Many teams are already past the point where each line can realistically be scrutinized; the volume of code being generated is increasing faster than our capacity to inspect it. Every AI-assisted coding session produces choices: naming decisions, structural decisions, abstraction decisions, dependency decisions. Some of these are good, some less so, and the ratio of decisions being made to decisions being reviewed by a human is growing.&lt;/p&gt;</description></item></channel></rss>