<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web02.fireside.fm</fireside:hostname>
    <fireside:genDate>Thu, 30 Apr 2026 18:22:12 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Software Defined Interviews - Episodes Tagged with “Pairing”</title>
    <link>https://www.softwaredefinedinterviews.com/tags/pairing</link>
    <pubDate>Thu, 03 Nov 2016 15:15:00 +0100</pubDate>
    <description>Deep discussions about technology, enterprise IT, and the like
</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>Deep discussions about technology, enterprise IT, and the like</itunes:subtitle>
    <itunes:author>Software Defined Talk</itunes:author>
    <itunes:summary>Deep discussions about technology, enterprise IT, and the like
</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/cover.jpg?v=7"/>
    <itunes:explicit>yes</itunes:explicit>
    <itunes:owner>
      <itunes:name>Software Defined Talk</itunes:name>
      <itunes:email>softwaredefinedinterviews@cote.wtf</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Business">
  <itunes:category text="Management"/>
</itunes:category>
<item>
  <title>Episode 16: Pair programing doesn't stink</title>
  <link>https://www.softwaredefinedinterviews.com/16</link>
  <guid isPermaLink="false">09772981-ad31-4cf4-b50f-c7623a72655c</guid>
  <pubDate>Thu, 03 Nov 2016 15:15:00 +0100</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/09772981-ad31-4cf4-b50f-c7623a72655c.mp3" length="7661160" type="audio/mp3"/>
  <itunes:episode>16</itunes:episode>
  <itunes:title>Pair programing doesn't stink</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do.</itunes:subtitle>
  <itunes:duration>7:08</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/0/09772981-ad31-4cf4-b50f-c7623a72655c/cover.jpg?v=1"/>
  <description>Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do. 
</description>
  <content:encoded>
    <![CDATA[<p>Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do.</p><p>Links:</p><ul><li><a title=" My Pairing column from October at The Register" rel="nofollow" href="http://www.theregister.co.uk/2016/10/18/pairing_programming_youll_never_guess_what_happens_next/"> My Pairing column from October at The Register</a> &mdash; The comments section is especially good for common sentiment about pair programming.</li><li><a title="Charles Lowell" rel="nofollow" href="http://twitter.com/cowboyd">Charles Lowell</a> &mdash; We used to do a podcast.</li><li><a title="Gartner survey on pair programming adoption" rel="nofollow" href="http://www.slideshare.net/cote/better-ways-of-doing-software/19">Gartner survey on pair programming adoption</a> &mdash; I got the number wrong: it's actually around 20%, not just 10%.</li><li><a title=" Mark Ardito goes over HCSC’s astonishing success with pair programming" rel="nofollow" href="https://www.youtube.com/watch?v=rGNlSCquZIc&amp;t=11m05s"> Mark Ardito goes over HCSC’s astonishing success with pair programming</a> &mdash; They thought it'd take 12-15 weeks to get their MVP done, but it actually took 5.5 to 6 weeks we finish.</li><li><a title="Selecting people for pair programming and their enthusiastic response" rel="nofollow" href="https://www.youtube.com/watch?v=rGNlSCquZIc&amp;t=26m35s">Selecting people for pair programming and their enthusiastic response</a> &mdash; More from Mark Ardito on HCSC's adoption of pair programming.</li><li><a title=" Phil Horowitz talks about how exhausting pairing is at first" rel="nofollow" href="http://www.informationweek.com/devops/project-management/adventures-in-pair-programming/a/d-id/1325577"> Phil Horowitz talks about how exhausting pairing is at first</a> &mdash; At Perforce: "This makes pair programming intense, especially at the beginning. At the end of the first day, I couldn't go home. Before I could face humans again, I put my phone on airplane mode, ignored my usual online accounts, and went to the gym for two hours of self-imposed isolation."</li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do.</p><p>Links:</p><ul><li><a title=" My Pairing column from October at The Register" rel="nofollow" href="http://www.theregister.co.uk/2016/10/18/pairing_programming_youll_never_guess_what_happens_next/"> My Pairing column from October at The Register</a> &mdash; The comments section is especially good for common sentiment about pair programming.</li><li><a title="Charles Lowell" rel="nofollow" href="http://twitter.com/cowboyd">Charles Lowell</a> &mdash; We used to do a podcast.</li><li><a title="Gartner survey on pair programming adoption" rel="nofollow" href="http://www.slideshare.net/cote/better-ways-of-doing-software/19">Gartner survey on pair programming adoption</a> &mdash; I got the number wrong: it's actually around 20%, not just 10%.</li><li><a title=" Mark Ardito goes over HCSC’s astonishing success with pair programming" rel="nofollow" href="https://www.youtube.com/watch?v=rGNlSCquZIc&amp;t=11m05s"> Mark Ardito goes over HCSC’s astonishing success with pair programming</a> &mdash; They thought it'd take 12-15 weeks to get their MVP done, but it actually took 5.5 to 6 weeks we finish.</li><li><a title="Selecting people for pair programming and their enthusiastic response" rel="nofollow" href="https://www.youtube.com/watch?v=rGNlSCquZIc&amp;t=26m35s">Selecting people for pair programming and their enthusiastic response</a> &mdash; More from Mark Ardito on HCSC's adoption of pair programming.</li><li><a title=" Phil Horowitz talks about how exhausting pairing is at first" rel="nofollow" href="http://www.informationweek.com/devops/project-management/adventures-in-pair-programming/a/d-id/1325577"> Phil Horowitz talks about how exhausting pairing is at first</a> &mdash; At Perforce: "This makes pair programming intense, especially at the beginning. At the end of the first day, I couldn't go home. Before I could face humans again, I put my phone on airplane mode, ignored my usual online accounts, and went to the gym for two hours of self-imposed isolation."</li></ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
