<?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 Techniques on No Semicolons</title><link>https://nosemicolons.com/tags/pair-programming-techniques/</link><description>Recent content in Pair Programming Techniques on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 24 Jun 2026 10:42:09 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/pair-programming-techniques/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Pairing Revolution: How Two Developers + One AI Model Beats Traditional Mob Programming</title><link>https://nosemicolons.com/posts/ai-code-generation-pairing-revolution/</link><pubDate>Wed, 24 Jun 2026 10:42:09 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-pairing-revolution/</guid><description>&lt;p>Ever tried explaining a complex algorithm to your pair programming partner, only to have them say &amp;ldquo;wait, what if we just ask the AI first?&amp;rdquo; That moment of realization hit me hard last month when my teammate Sarah and I were struggling with a gnarly React performance issue. Instead of our usual back-and-forth debugging dance, we pulled Claude into our session as a third team member.&lt;/p>
&lt;p>What happened next completely changed how I think about developer collaboration.&lt;/p></description></item></channel></rss>