Pair Programming
Published ....
Last modified ....
Share this post on BlueskySee discussion on Bluesky
I found this tweet earlier today that really accurately describes some of my thinking about pair programming as of late:
I did pair programming exclusively for years at Pivotal.
It’s an incredible tool.
It’s also a fabulous way to never ship anything: 8 engineers (4 pairs) on a team have a really hard time gaining any consensus or direction when everything is essentially decided by committee. https://t.co/Nmxk1bMzfS
— John McBride (@johncodezzz)
November 25, 2023
However, I used to think a bit differently about pair programming so I figured it'd be worth talking about why my opinion changed on the topic.
Before digging in though, I realized that this isn't the first time I went to write about pair programming, I even have a stub of an article here (just over 2 years old at this point!), and also a semi-popular post on (which is almost 3 years old now!).