A mystery company is doing what most software teams dream of cutting feature lead time to less than one-third, reducing bugs, and shipping more features per release. Their secret? Pair programming.

In this episode, Dave Farley explores how this team used Extreme Programming (XP) principles to transform their software development process, proving that collaboration and continuous improvement can achieve dramatic results. Learn how working in pairs can accelerate feedback, improve code quality, and help developers write better software faster.

Whether you’re a developer, software engineer, or technical leader, this video will change how you think about teamwork, productivity, and sustainable delivery.

-

Dave on X ➡️ https://x.com/davefarley77
Dave on LinkedIn ➡️ https://www.linkedin.com/in/dave-farley-a67927/
Dave on bluesky ➡️ https://bsky.app/profile/davefarley77.bsky.social

Modern Software Engineering on X ➡️ https://x.com/ModernSoftwareX
Modern Software Engineering on LinkedIn ➡️ https://www.linkedin.com/company/modern-software-engineering
Modern Software Engineering on bluesky ➡️ https://bsky.app/profile/modernswe.bsky.social

-

⭐ PATREON:

Join the Continuous Delivery community and access extra perks & content! ➡️ https://bit.ly/ContinuousDeliveryPatreon 

🎥 Join Us On TikTok ➡️ https://www.tiktok.com/@modern.s.engineering

-

CHANNEL SPONSORS:

This video is sponsored by Mailtrap - an Email Platform developers love. Go for fast email delivery, high inboxing rates, and live 24/7 expert support.
Check the details ➡️ https://l.rw.rw/mse_6

Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0

TransFICC provides low-latency connectivity, automated trading workflows and e-trading systems for Fixed Income and Derivatives. TransFICC resolves the issue of market fragmentation by providing banks and asset managers with a unified low-latency, robust and scalable API, which provides connectivity to multiple trading venues while supporting numerous complex workflows across asset classes such as Rates and Credit Bonds, Repos, Mortgage-Backed Securities and Interest Rate Swaps ➡️ https://transficc.com

-

👕 T-SHIRTS:

A fan of the T-shirts I wear in my videos? Grab your own, at reduced prices EXCLUSIVE TO CONTINUOUS DELIVERY FOLLOWERS! Get money off the already reasonably priced t-shirts!

🔗 Check out their collection HERE: ➡️ https://bit.ly/3Uby9iA
🚨 DON'T FORGET TO USE THIS DISCOUNT CODE: ContinuousDelivery

-


🖇️  LINKS:

🔗 "We stopped doing PRs" https://youtu.be/xS6yH0VqJjw
🔗 "The pros and cons of Pair programming" https://youtu.be/fbxMV76e7
🔗 "You must be crazy to do pair programming" https://youtu.be/aItVJprLYkg
🔗 “Pair Programming Increases ‘Flow’”  ➡️ https://journals.sagepub.com/doi/abs/10.1177/0735633120949788
🔗 "What Makes Teams High Performers?" ➡️  https://rework.withgoogle.com/en/guides/understanding-team-effectiveness#introduction 

-

BOOKS:

📖 Dave’s Book "Modern Software Engineering" is available as paperback, or kindle here ➡️ https://amzn.to/3DwdwT3 
and NOW as an AUDIOBOOK available on iTunes, Amazon and Audible.

📖 The original, award-winning "Continuous Delivery" book by Dave Farley and Jez Humble ➡️ https://amzn.to/2WxRYmx

📖 "Continuous Delivery Pipelines" by Dave Farley
Paperback ➡️ https://amzn.to/3gIULlA
ebook version ➡️ https://leanpub.com/cd-pipelines

📖 "The Software Developers’ Guidebook
Amazon ➡️ https://amzn.to/4f9ozFK
ebook version ➡️ https://leanpub.com/softwaredevelopersguidebook

NOTE: If you click on one of the Amazon Affiliate links and buy the book, Continuous Delivery Ltd. will get a small fee for the recommendation with NO increase in cost to you.

-

#developer #softwareenineer #softwareengineering #softwaredeveloper #softwaredevelopment #programming #coding #code

Continuous Delivery

A well-known web company reduced average feature development time from 151 hours to 44 hours by adopting pair programming, while simultaneously decreasing production bugs and eliminating code review bottlenecks. The experiment, initially met with skepticism about productivity concerns, proved that two developers working together could deliver features faster and with higher quality than solo developers going through traditional pull request workflows. The company analyzed over 5,000 pull requests and found that larger code changes received fewer meaningful review comments, mirroring research showing code review effectiveness diminishes with change size.

This Company Tripled Developer Speed By Adopting THIS Practice

It’s been done for decades. We did it in some workplace I was at some ~15 years ago. It’s fun but stressful because you cannot simply sit quietly and think for a long duration as the other person’s presence can feel “heavy” and the person who is typing might simply try to maintain the “flow” of code rather than sit and contemplate on better options, which will “bore” the other person.
Sometimes the other person is very pushy and the one typing has a weak personality and while being “better”, the weaker one will adhere to the stronger one and won’t fully express their potential.
I think pair programming have success in making average-quality code (“good enough”) rather than good code.