--- title: This Company Tripled Developer Speed By Adopting THIS... description: A well-known web company reduced average feature development time from 151 hours to 44 hours by adopting pair programming, while simultaneously decreasing... canonical: https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: This Company Tripled Developer Speed By Adopting THIS Practice | daily.dev og:description: A well-known web company reduced average feature development time from 151 hours to 44 hours by adopting pair programming, while simultaneously decreasing... og:url: https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl og:image: https://api.daily.dev/og/posts/E6QixEHJL.png og:image:alt: This Company Tripled Developer Speed By Adopting THIS Practice og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # This Company Tripled Developer Speed By Adopting THIS Practice **[Continuous Delivery](https://daily.dev/sources/continuousdelivery)** · 15 min read · 35 upvotes · 3 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@denisb0** · 5 upvotes > Did they triple the pay too? **@yaireo** · 0 upvotes > 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... ## Similar posts on daily.dev - [The price of mandatory code reviews](https://daily.dev/posts/the-price-of-mandatory-code-reviews-pvm89ysyt) · Manager.dev · 46 upvotes · 3 comments - [Blog: The AI Velocity Paradox: Why Your Team Ships Slower When Developers Move Faster](https://daily.dev/posts/blog-the-ai-velocity-paradox-why-your-team-ships-slower-when-developers-move-faster-wtxobitud) · Wawandco · 1 upvotes · 1 comments - [Trunk-Based Development: Why Most Teams Think They Use It \(But Don’t\)](https://daily.dev/posts/trunk-based-development-why-most-teams-think-they-use-it-but-don-t--lfl8cgutz) · CodeCraft Diary · 17 upvotes · 2 comments - [If You Think AI Made You a 10x Developer, Pair Program More](https://daily.dev/posts/if-you-think-ai-made-you-a-10x-developer-pair-program-more-bkze4sprb) · Atomic Spin · 0 upvotes · 0 comments --- Tags: [#productivity](https://daily.dev/tags/productivity), [#cicd](https://daily.dev/tags/cicd), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"This Company Tripled Developer Speed By Adopting THIS Practice","url":"https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl"},"datePublished":"2025-11-05T19:12:31.667Z","dateModified":"2025-11-05T19:12:52.246Z","description":"A well-known web company reduced average feature development time from 151 hours to 44 hours by adopting pair programming, while simultaneously decreasing...","image":"https://i.ytimg.com/vi/GVmjNk-gFU4/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/GVmjNk-gFU4/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Continuous Delivery","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Continuous Delivery","logo":"https://media.daily.dev/image/upload/s---b6TAqpH--/f_auto/v1730404995/logos/continuousdelivery","url":"https://daily.dev/sources/continuousdelivery"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":35},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"productivity,cicd,code-review","timeRequired":"PT15M","video":{"@type":"VideoObject","name":"This Company Tripled Developer Speed By Adopting THIS Practice","description":"A well-known web company reduced average feature development time from 151 hours to 44 hours by adopting pair programming, while simultaneously decreasing...","thumbnailUrl":"https://i.ytimg.com/vi/GVmjNk-gFU4/sddefault.jpg","uploadDate":"2025-11-05T19:12:31.667Z","duration":"PT15M","url":"https://api.daily.dev/r/E6QixEHJL","embedUrl":"https://www.youtube.com/embed/GVmjNk-gFU4"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Continuous Delivery","item":"https://daily.dev/sources/continuousdelivery"},{"@type":"ListItem","position":3,"name":"This Company Tripled Developer Speed By Adopting THIS Practice"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/this-company-tripled-developer-speed-by-adopting-this-practice-e6qixehjl","comment":[{"@type":"Comment","text":"Did they triple the pay too?","datePublished":"2025-11-06T19:03:23.965Z","url":"https://daily.dev/posts/E6QixEHJL#c-17onodsoO","author":{"@type":"Person","name":"Denis Bolkovskis","url":"https://daily.dev/denisb0","image":"https://media.daily.dev/image/upload/s--PGCuYx85--/f_auto,q_auto/v1/avatars/avatar_yRuVFf6IbfTylBjx9Dzvt"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5}},{"@type":"Comment","text":"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.\nSometimes 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.\nI think pair programming have success in making average-quality code (“good enough”) rather than good code.","datePublished":"2025-12-23T09:00:02.650Z","url":"https://daily.dev/posts/E6QixEHJL#c-I2Zp8zcqx","author":{"@type":"Person","name":"Yair Even Or","url":"https://daily.dev/yaireo","image":"https://avatars.githubusercontent.com/u/845031?v=4"}}]} ```