<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Architecture on Vic Boomer</title>
    <link>https://vicboomer.com/tags/architecture/</link>
    <description>Recent content in Architecture on Vic Boomer</description>
    <generator>Hugo</generator>
    <language>nl</language>
    <lastBuildDate>Tue, 10 Mar 2026 09:00:00 +0200</lastBuildDate>
    <atom:link href="https://vicboomer.com/tags/architecture/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Agents Aren&#39;t Tools</title>
      <link>https://vicboomer.com/essays/en-why-agents-arent-tools/</link>
      <pubDate>Tue, 10 Mar 2026 09:00:00 +0200</pubDate>
      <guid>https://vicboomer.com/essays/en-why-agents-arent-tools/</guid>
      <description>&lt;p&gt;Most organizations treat AI agents as faster tools. That&amp;rsquo;s a fundamental misconception.&lt;/p&gt;&#xA;&lt;p&gt;A tool is something you do something &lt;em&gt;with&lt;/em&gt;. An agent does something &lt;em&gt;for&lt;/em&gt; you. That sounds like a small difference, but it changes everything: the architecture, the governance, the error handling, and above all the way you think about reliability.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tool-thinking&#34;&gt;Tool thinking&lt;/h2&gt;&#xA;&lt;p&gt;When an organization deploys an &amp;ldquo;AI tool&amp;rdquo;, people think in terms of input and output. You put something in, you get something out. The human stays the operator.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
