<?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>Sop on Kevin Sookocheff</title>
    <link>https://sookocheff.com/tags/sop/</link>
    <description>Recent content in Sop on Kevin Sookocheff</description>
    <generator>Hugo</generator>
    <language>en-ca</language>
    <lastBuildDate>Thu, 12 Nov 2026 06:41:48 +0000</lastBuildDate>
    <atom:link href="https://sookocheff.com/tags/sop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing an Autonomous Development Team</title>
      <link>https://sookocheff.com/post/ai/designing-an-autonomous-development-team/</link>
      <pubDate>Thu, 12 Nov 2026 06:41:48 +0000</pubDate>
      <guid>https://sookocheff.com/post/ai/designing-an-autonomous-development-team/</guid>
      <description>&lt;p&gt;When using LLMs for software development, it is easy and natural to use a
single agent to inspect the codebase, make a plan, write some code, run
tests, and open a pull request. This works surprisingly well, but it also
collapses an entire software development process into one conversation.&lt;/p&gt;
&lt;p&gt;A real development team usually has a few more boundaries. Someone thinks
through the design. Someone implements it. Someone else reviews the
implementation. When something is unclear, we communicate the problem and
resolve it rather than silently making assumptions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
