<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pair-Programming on Yesterday I was wrong</title>
    <link>/tags/pair-programming/</link>
    <description>Recent content in Pair-Programming on Yesterday I was wrong</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 27 Apr 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/pair-programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Pair Programming to Co-Steering</title>
      <link>/2026/04/27/from-pair-programming-to-co-steering/</link>
      <pubDate>Mon, 27 Apr 2026 09:00:00 +0000</pubDate>
      <guid>/2026/04/27/from-pair-programming-to-co-steering/</guid>
      <description>&lt;p&gt;This is part 2 of a 5-part series on agentic engineering. &lt;a href=&#34;/2026/04/26/from-agile-engineering-to-agentic-engineering/&#34;&gt;Part 1&lt;/a&gt; made the case that Agile values still matter; the mechanisms are what change. This post takes the most contested of those mechanisms — pair programming — and looks at what happens to it when one of the &amp;ldquo;pair&amp;rdquo; doesn&amp;rsquo;t need a keyboard.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been a fan of pair programming for a long time. At Triptease we&amp;rsquo;ve leaned on it because it improves quality, accelerates learning, spreads context, builds resilience, and quietly does a lot of work for team cohesion. Those outcomes still matter.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
