# pair\_programming Published articles for pair\_programming. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Extreme Programming remains relevant for building software teams in 2026 DevFeed: [Extreme Programming remains relevant for building software teams in 2026]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-18T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Programming](), [Development](), [Refactoring](), [Test-driven development](), [pair\_programming](), [Code review]() Tags: [code](), [code-quality](), [development](), [pair-programming](), [programming](), [redesign](), [tdd]() ### AI overview The author revisits Kent Beck's Extreme Programming after experiencing frustration with Scrum and the pressures facing modern engineering teams. The article argues that XP remains relevant because it combines five values, 14 principles, and numerous practices aimed at improving both software and team life, rather than reducing the methodology to TDD and pair programming alone. ### Source excerpt A method created 30 years ago is still your best guide for building software ## AI Coding Best Practices for Today DevFeed: [AI Coding Best Practices for Today]() Original publisher: [Read original article]() Published: 2026-02-25T21:59:05Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [ai-coding](), [Artificial Intelligence](), [coding](), [GitHub Copilot](), [Claude](), [cursor](), [Development](), [Vulnerabilities](), [Code](), [Security](), [pair\_programming](), [Maintainability]() Tags: [ai](), [ai-coding](), [ai-coding-assistants](), [best-practices](), [claude](), [code](), [coding](), [copilot](), [cursor](), [developers](), [github-copilot](), [llms](), [maintainability](), [pair-programming](), [research](), [uncategorized]() ### AI overview A practical guide to using AI coding assistants such as GitHub Copilot, Claude, and Cursor while managing risks in code quality, deprecated APIs, security, performance, and maintainability. It emphasizes human responsibility, reviewing all generated code, and verifying it with tests, linters, and personal judgment. ### Source excerpt Why This Document Exists AI coding assistants like GitHub Copilot, Claude, Cursor, and others can significantly accelerate development. However, research shows they also introduce systematic risks: ## Transparency, autonomy, responsiveness, and education: How the Aha! engineering team works DevFeed: [Transparency, autonomy, responsiveness, and education: How the Aha! engineering team works]() Original publisher: [Read original article]() Published: 2024-10-28T00:00:00Z Content type: opinion Language: en Sources: [Aha! Engineering Blog]() Topics: [Programming](), [Self-organizing Team](), [Agile](), [pair\_programming](), [Code](), [App]() Tags: [agile](), [approach](), [engineering](), [meetings](), [pair-programming](), [product](), [programming](), [security](), [team](), [teams](), [transparency](), [work]() ### AI overview The article explains how Aha!'s engineering team combines individual, pair, and team-based work. Engineers present their work in weekly meetings, retain ownership of code, and share knowledge across the organization. Small agile teams align with product areas and infrastructure, while rotating support responsibilities provide broader exposure. Product managers, designers, and engineers prioritize and scope work collaboratively. ### Source excerpt Organizations have many different ways to approach how teammates write code. You have individual silos, pair programming, team-based work, and black box interfaces where you have no idea how the other team is structured. We use a mix of these approa ## Replay 2024 recap: Day 1 DevFeed: [Replay 2024 recap: Day 1]() Original publisher: [Read original article]() Author: Alice Yin Published: 2024-09-19T04:00:00Z Content type: news Language: en Sources: [Temporal Blog]() Topics: [distributed-systems](), [Cloud](), [Scalability](), [Security](), [Self-hosted](), [API keys](), [Google](), [Google Cloud Platform (GCP)]() Tags: [api](), [api-keys](), [architecture](), [cloud](), [community](), [conference](), [high-availability](), [pair-programming](), [recap](), [scalability]() ### AI overview A recap of Day 1 of Temporal's Replay 2024 conference covering keynote announcements, Temporal Cloud updates, distributed-systems challenges, and sessions on platform teams and self-hosted clusters. ### Source excerpt Get the top highlights and key takeaways from Day 1 of Temporal's annual community conference. ## Who Benefits Most from Cursor, Copilot, and Other AI Coding Assistants? DevFeed: [Who Benefits Most from Cursor, Copilot, and Other AI Coding Assistants?]() Original publisher: [Read original article]() Published: 2024-08-31T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [cursor](), [Artificial Intelligence](), [Large Language Model](), [GitHub Copilot](), [pair\_programming](), [Unit testing]() Tags: [ai](), [copilot](), [cursor](), [llm](), [pair-programming](), [unit-testing]() ### AI overview This opinion article argues that the benefits of AI coding assistants such as Cursor and GitHub Copilot depend less on whether a programmer is simply good or bad and more on their strengths, weaknesses, temperament, and personality. It compares these tools with unit testing and pair programming, emphasizing that AI assistants can provide broad technical knowledge, speed, and brainstorming while still making mistakes and struggling with design and innovation. ### Source excerpt Who wins now that Cursor is out? Good programmers? Bad programmers? Here, I make the case that it is more about your tempermant and personality traits. If you're good in the places where the AI is weak, you'll knock it out of the park. ## Increase Engineering Productivity by 50% Through Focus and Flow DevFeed: [Increase Engineering Productivity by 50% Through Focus and Flow]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-06-01T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [developer-productivity](), [code productivity](), [pair\_programming](), [context](), [meetings](), [Documentation](), [real-time]() Tags: [collaboration](), [collaboration-communication-continuous-deployment-developer-experience-developer-productivity-e](), [documentation](), [engineering-productivity](), [flow](), [focus](), [pair-programming](), [real-time]() ### AI overview This article discusses how focus and flow affect developer productivity and presents practical organizational ideas for improving them. It emphasizes collaboration, team or pair programming, reducing distractions and context switching, real-time reviews, and useful documentation. ### Source excerpt Increase Engineering Productivity by 50% Through Focus and Flow Creating an environment where developers can maintain focus and achieve flow can lead to a 50% increase in productivity, as research suggests. But how do we create such an environment? ## How Skyscanner's all-day video call supports collaboration and knowledge sharing DevFeed: [How Skyscanner's all-day video call supports collaboration and knowledge sharing]() Original publisher: [Read original article]() Author: Skyscanner Engineering Published: 2023-08-09T12:34:59Z Content type: opinion Language: en Sources: [Stories by Skyscanner Engineering on Medium]() Topics: [Development](), [pair\_programming](), [Programming](), [meetings]() Tags: [collaboration](), [development](), [hybrid](), [knowledge-sharing](), [meetings](), [pair-programming](), [tech](), [virtual-office]() ### AI overview An employee describes how Skyscanner's hybrid team uses an all-day video call as a virtual office. The call helps colleagues across UK cities collaborate, share knowledge, support training, and participate in mob or pair programming. ### Source excerpt by Anthony Byledbal In the virtual office -- iStock Note: At Skyscanner, our teams work using a hybrid model. When not in the office, we want optimise our experience and keep close connection with our team members Video calls are usually meetings. An invitation is sent to participants and, on the scheduled day and time, all join for a limited period of time. However, in my team at Skyscanner, we as a team have decided to take a step further by introducing an all-day-long video call. The operating instructions are short: the first person to start its day, starts the call; the last person to finish, closes the call. This online tool has proven very successful with regards to employee collaboration, training enhancement, boosting morale and overall sense of engagement and positive team spirit. I was not used to working this way, but very quickly I have noticed the positive impact it had on me and my development. Before changing career from archaeology and moving to IT, I was unfamiliar with different kinds of online tools used in a working environment. I naively interpreted them as a poor management: I thought it was a way to track what me and my colleagues were doing. However, my experience in joining this call proved me wrong. Members of my squad created this online headquarter to connect their colleagues located across different cities around the United Kingdom in hope of improving communication, morale and collaboration within the team. A Shared Working Environment The call brings colleagues together. It is our virtual office where we feel less apart from each other. More importantly, this online space facilitates our daily work and knowledge sharing. It is good to see more experienced colleagues coding. Sharing screens is something our team does all day long, it immerses everyone into the code. From new joiners to senior engineers, everyone values this precious time because it allows us to ask questions and rise concerns. Most of the time, this provides us with an ## Imperfect #14: How to map dependencies DevFeed: [Imperfect #14: How to map dependencies]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2023-07-07T13:33:59Z Content type: tutorial Language: en Sources: [Pedro Gil Carvalho]() Topics: [Architecture & Design](), [microservices architecture](), [Microservice](), [interfaces](), [API](), [Database]() Tags: [api](), [architecture](), [awareness](), [changes](), [database](), [dependencies](), [distributed](), [issue-tracker](), [map](), [microservices](), [microservices-architecture](), [monitor](), [monolith](), [pair-programming]() ### AI overview The article explains how to map service dependencies to help identify and avoid distributed monoliths. It recommends team-by-team architecture reviews, collaboratively maintained diagrams, monitoring connected interfaces, and tracking dependencies in a simple spreadsheet. ### Source excerpt Avoiding the distributed monolith antipattern requires great situational awareness. Today we go over what that means, how architecture reviews can help, and one simple way to anticipate dependencies. ## AI-assisted programming can speed development while increasing abstraction and technical debt DevFeed: [AI-assisted programming can speed development while increasing abstraction and technical debt]() Original publisher: [Read original article]() Author: Adam Published: 2023-06-16T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Artificial Intelligence](), [GitHub Copilot](), [ChatGPT](), [jupyter notebooks](), [Application Security](), [Python](), [pair\_programming](), [Programming]() Tags: [ai](), [appsec](), [chatgpt](), [copilot](), [jupyter-notebooks](), [pair-programming](), [programming](), [python]() ### AI overview The author reflects on using ChatGPT, GitHub Copilot, pair programming, and Jupyter Notebooks while learning Python and producing graphs. The experience accelerated development and debugging, but raised concerns about code quality, application security, abstraction, and the faster accumulation of technical debt. ### Source excerpt AI will be the high interest credit card of 2023 I haven't done a lot of work in Python, and I've never used it to produce graphs. But after an hour of pair programming and then using Chatgpt and Github Copilot got me quite far in writing a set of Jupyter Notebooks, and dramatically shrunk the effort to use and debug a new tool. I wanted to record some thoughts on the experience, and what it means for programming and for application security. ## A practical example of using AI for coding DevFeed: [A practical example of using AI for coding]() Original publisher: [Read original article]() Author: Mike Published: 2023-06-14T03:34:57Z Content type: tutorial Language: en Sources: [Dev Details]() Topics: [ai-coding](), [Artificial Intelligence](), [Development](), [coding](), [Programming](), [pair\_programming]() Tags: [ai](), [ai-coding](), [coding](), [developing](), [example](), [pair-programming](), [practical](), [programming]() ### AI overview A practical tutorial on using ChatGPT and other large language models in software development. It presents an end-to-end application walkthrough and recommends treating AI as a coding companion while remaining engaged, precise, and able to review the generated code. ### Source excerpt An end-to-end walkthrough of designing, developing, and testing a simple application with the help of AI. ## The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance DevFeed: [The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-02-18T06:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Development](), [pair\_programming](), [Programming]() Tags: [collaboration](), [collaboration-culture-ensemble-programming-practices-remote-work-developer-productivity-organi](), [developers](), [pair-programming](), [productivity](), [remote-work](), [teamwork](), [video-conferencing]() ### AI overview The article describes claimed benefits of remote work for developer teams, including reduced commuting stress, flexible scheduling, fewer office distractions, and improved work-life balance. It also explains how digital collaboration tools can support real-time teamwork and pair programming across locations. ### Source excerpt The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance In today's fast-paced and constantly changing world, many organisations are rethinking traditional work arrangements and embracing the benefits of remote work. ## How To Have A Compelling Interview Experience DevFeed: [How To Have A Compelling Interview Experience]() Original publisher: [Read original article]() Author: Rahul Pandey Published: 2022-08-31T23:15:19Z Content type: tutorial Language: en Sources: [Alex Chiou]() Topics: [Programming](), [pair\_programming](), [Software]() Tags: [advice](), [career](), [how-to](), [interview](), [pair-programming]() ### AI overview A Tech Career Growth newsletter discusses how interviewers can balance useful evaluation with a positive candidate experience, including careful use of hints and pair programming. It also advises candidates to communicate clearly and avoid fishing for hints. ### Source excerpt Welcome to another edition of the Tech Career Growth newsletter - we help software engineers find career success faster than tech companies kill products [1], [2], [3]. ## Efficiently Learning IDE Keyboard Shortcuts DevFeed: [Efficiently Learning IDE Keyboard Shortcuts]() Original publisher: [Read original article]() Author: Derek Lee Published: 2022-01-29T03:00:00Z Content type: tutorial Language: en Sources: [art and science of coding]() Topics: [ide](), [Learning](), [Development](), [pair\_programming](), [Tool]() Tags: [art](), [developer](), [development](), [ide](), [keyboard](), [keyboard-shortcuts](), [learning](), [pair-programming](), [plugin](), [plugins](), [productivity]() ### AI overview This tutorial explains how developers can learn IDE keyboard shortcuts through pair programming, IDE feedback, menus, and plugins such as Presentation Assistant, KeyLimePie, and Key Promoter X. ### Source excerpt Super charge your development productivity! ## Trivago Tech Week DevFeed: [Trivago Tech Week]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2021-01-06T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Hackathon](), [Programming](), [dropbox](), [zoom]() Tags: [collaboration](), [communication](), [conferences](), [engineering-culture](), [events](), [hackathon](), [interviews](), [pair-programming](), [tech](), [virtual](), [virtual-event](), [workshops](), [zoom]() ### AI overview Trivago describes its 2020 virtual tech week, organized to restore collaboration and informal exchange during a period of remote meetings. The event included talks, forums, a virtual hackathon, workshops, and a scavenger-hunt-style tech challenge, with reported participation and session figures. ### Source excerpt One of my favorite events throughout the year is the trivago tech get together. It's the one time where we all get together to celebrate tech. Here are some impressions from 2019: ## 5 Tips to Boost Productivity When Working Remotely as an Engineer DevFeed: [5 Tips to Boost Productivity When Working Remotely as an Engineer]() Original publisher: [Read original article]() Author: Hendrik Kleinwächter Published: 2020-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Programming](), [async](), [Terminal](), [Vim](), [Emacs]() Tags: [async](), [code](), [communication](), [emacs](), [engineering-culture](), [pair-programming](), [productivity](), [programming](), [terminal](), [tips](), [vim](), [work]() ### AI overview An engineer shares practical advice for working remotely, including communicating more, using asynchronous communication, seeking help early on technical decisions, pairing through terminal sessions, and working together on calls. ### Source excerpt Throughout my career, I've had times where I worked 100% remotely. Overall working remotely can have benefits and even make you more productive as an engineer. I would like to share 5 tips that ... ## Tuple as a Pair-Programming Tool: Benefits and Limitations DevFeed: [Tuple as a Pair-Programming Tool: Benefits and Limitations]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-22T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Programming](), [Software](), [ui](), [Slack](), [Google Meet](), [osx]() Tags: [apple](), [developer](), [interface](), [osx](), [pair-programming](), [programming](), [slack](), [software](), [software-engineering](), [techniques](), [user-interface]() ### AI overview An opinion article evaluates Tuple for remote pair programming, praising its unobtrusive design, performance, audio quality, and speed. It also notes that Tuple has a monthly fee and supports only OSX. ### Source excerpt As I've written in the past, I am an unabashed fan of pair programming. Pair programming is one of the few techniques that I can credibly point to that really, really, really improves software quality. And since I'm a remote developer, I really, really need good pairing tools. The unfortunate reality of pair programming is that there really aren't good tools for pairing - until Tuple. The current suite of tools for pairing include things like: Google Hangouts / Google Meet - slow, craptastic user interface Skype - don't get me started; Microsoft gutted Skype and left it for dead in a alley Slack - only available on paid slack; slow, uses a lot of CPU While there have been good tools for pairing in the past, notably ScreenHero and Apple Remote Desktop, none of these tools are available today. ScreenHero got bought by Slack and "integrated" while Apple Remote Desktop, well, I seem to have been the only user who remembers it. The current tool I'm using is Tuple and it is simply outstanding. Here are some of the reasons: It just works. For pairing to be something that you just do on an ad hoc basis, the tool needs to be utterly unobtrusive. Tuple is brilliantly in its minimalism. It doesn't slow everything on the machine to a crawl. The audio quality is fantastic. It is fast. Here are the disadvantages: It is expensive; the model is a monthly fee. It is OSX only. ## When to pair program DevFeed: [When to pair program]() Original publisher: [Read original article]() Author: Jack Tarantino Published: 2017-03-14T20:59:32Z Content type: opinion Language: en Sources: [Jacopo Tarantino]() Topics: [pair\_programming](), [Development](), [Code quality]() Tags: [best-practices](), [bugs](), [development](), [pair-programming](), [pairing](), [process](), [programming](), [quality]() ### AI overview An opinion article examines when pair programming is useful. It describes pairing as an Extreme Programming practice and argues that working with a peer can improve software quality, reduce bugs, and limit technical debt. ### Source excerpt This post is another one brought to you by the good people at InRhythm. If you're an engineer that likes writing and building strong, happy culture focused on learning and growth you should apply! I like working with smart, passionate people :). Lots of companies embrace pair programming as a way ## Weighing in on Long Live Testing DevFeed: [Weighing in on Long Live Testing]() Original publisher: [Read original article]() Author: Jay (noreply@blogger.com) Published: 2014-05-19T16:52:00Z Content type: opinion Language: en Sources: [Jay Fields]() Topics: [Testing](), [Test-driven development](), [unit tests](), [Refactoring](), [pair\_programming]() Tags: [behavior](), [code-coverage](), [java](), [pair-programming](), [refactoring](), [tdd](), [testing](), [unit-testing](), [unit-tests]() ### AI overview The author argues that test-driven development and testing practices should be chosen based on their purpose and context rather than followed dogmatically. Drawing on experience with a simple internal application, the article emphasizes asking why a test is being written and identifies goals such as validation, regression prevention, coverage, legacy-code refactoring, and documenting system behavior. ### Source excerpt DHH recently wrote a provocative piece that gave some views into how he does and doesn't test these days. While I don't think I agree with him completely, I applaud his willingness to speak out against TDD dogma. I've written publicly about not buying the pair-programming dogma, but I hadn't previously been brave enough to admit that I no longer TDD the vast majority of the time. The truth is, I haven't been dogmatic about TDD in quite some time. Over 6 years ago I was on a ThoughtWorks project where I couldn't think of a single good reason to TDD the code I was working on. To be honest, there weren't really any reasons that motivated me to write tests at all. We were working on a fairly simple, internal application. They wanted software as fast as they could possibly get it, and didn't care if it crashed fairly often. We kept everything simple, manually tested new features through the UI, and kept our customer's very happy. There were plenty of reasons that we could have written tests. Reasons that I expect people will want to yell at me right now. To me, that's actually the interesting, and missing part, of the latest debate on TDD. I don't see people asking: Why are we writing this test? Is TDD good or bad? That depends; TDD is just a tool, and often the individual is the determining factor when it comes to how effective a tool is. If we start asking "Why?", it's possible to see how TDD could be good for some people, and bad for DHH. I've been quietly writing a book on Working Effectively with Unit Tests, and I'll have to admit that it was really, really hard not to jump into the conversation with some of the content I've recently written. Specifically, I think this paragraph from the Preface could go a long way to helping people understand an opposing argument. Why Test? The answer was easy for me: Refactoring told me to. Unfortunately, doing something strictly because someone or something told you to is possibly the worst approach you could take. The more time ## FINN's Migration from Subversion to Git: Workflow and Productivity Benefits DevFeed: [FINN's Migration from Subversion to Git: Workflow and Productivity Benefits]() Original publisher: [Read original article]() Author: mick Published: 2013-03-20T11:14:08Z Content type: opinion Language: en Sources: [Finn.no]() Topics: [Git](), [CI/CD](), [Programming]() Tags: [coding](), [commit](), [continuous-deployment](), [developers](), [docs](), [git](), [pair-programming](), [programming](), [repositories](), [review](), [stable](), [tests]() ### AI overview FINN describes its migration from Subversion to Git, focusing on peer review, private repositories, branching, and individual productivity. The article also explains using feature branches with squashed or rebased changesets to support cleaner history and continuous deployment. ### Source excerpt "There is no way to do CVS right." - Linus FINN is migrating from subversion to the ever trendy git. We've waited years for it to happen, here we'll try to highlight why and how we are doing it. Working together There's no doubt that git gives us a cleaner way of working on top of each other. Wherever you promote peer review you need a way of working with changesets from one computer to the next without having to commit to and via the trunk where everyone is affected. Creating custom branches comes with too much (real or perceived) overhead, so the approach at best falls to throwing patches around. Coming away from a pair-programming session it's better when developers go back to their own desk with such a patch so they can work on it a bit more and finish it properly with tests, docs, and a healthy dose of clean coding. It properly entitles them as the author rather than appearing as if someone else took over and committed their work. Git's decentralisation of repositories provides the cleaner way by replacing these patches with private repositories and its easy to use branches. Individual productivity Git improves the individual's productivity with benefits of stashing, squashing, reseting, and rebasing. A number of programmers for a number of years were already on the bandwagon using git-svn against our subversion repositories. This was real proof of the benefits, given the headaches of git-svn (can't move files and renaming files gives corrupted repositories) With Git, work is encouraged to be done on feature branches and merged in to master as complete (squashed/rebased) changesets with clean and summarised commit messages. This improves efforts towards continuous deployment due to a more stable HEAD. Rolling back any individual feature regardless of its age is a far more manageable task. By squashing all those checkpoint commits we typically make we get more meaningful, contextual, and accurate commit messages. Reading isolated and complete changesets provides ## Petit retour sur le pair-programming DevFeed: [Petit retour sur le pair-programming]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2010-07-11T21:44:41Z Content type: opinion Language: fr Sources: [The Coffee Workshop]() Topics: [Programming](), [Test-driven development](), [Refactoring](), [maintenance]() Tags: [maintenance](), [pair](), [pair-programming](), [programming](), [refactoring](), [tdd]() ### AI overview The author reflects on pair programming after more than a year working in an agile Scrum context. The article discusses pair-architecturing and pair-analysing as related practices for sharing knowledge, challenging ideas, and handling complex maintenance work. ### Source excerpt Lors de ma mission précédente, une des unités business a décidé d'investir dans Scrum, avec ce changement de méthodologie, les équipes de développement étant relativement enthousiastes, ont été formées au TDD et au pair-programming. Une discussion avec un pote, nous a amené à parler du pair-architecturing, ou la confrontation des idées, le challenge apporté par son alter-ego, m'a conduit à écrire ce petit retour à propos du pair-programming, et pourquoi l'appliquer à d'autres disciplines n'est pas une mauvaise idée, au contraire.