<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Agents on lgovea</title>
    <link>https://lgovea.com/tags/agents/</link>
    <description>Recent content in Agents on lgovea</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>2026 lgovea</copyright>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lgovea.com/tags/agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>You Cannot Outsource Understanding</title>
      <link>https://lgovea.com/posts/you-cannot-outsource-understanding/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://lgovea.com/posts/you-cannot-outsource-understanding/</guid>
      <description>&lt;p&gt;I’m in the middle of a deployment right now. Someone handed me a project I did not build. Pressure is on, and the timeline is short. The fastest path: tell an AI agent to deploy it, walk away, and come back once it’s ready. That’s the pitch, anyway. In practice this could work or not. In both cases, I’ll still be accountable for the output.&lt;/p&gt;
&lt;p&gt;So I’m not doing that. I’m spending the first hours asking it to explain the architecture, the dependencies, and why things are where they are. It feels slower. It probably is slower, today.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
