Skip to main content

Why pair programming should be your default way of working

Although pair programming is not a new (software development) practice, I don't see it used that often at my clients. I think that the main reason for this is that because not that many developers tried it and therefore never experienced the benefits of pair programming.

Unknown is unloved.

But I experienced first handed that once you get comfortable with pair programming, you don’t want to go back. Most teams I worked with that started using it continued with the practice; sometimes partially sometimes full time.

 


Benefits of pair programming

Pair programming has several key benefits and purposes, which can significantly enhance the efficiency and effectiveness of development teams.

The Power of Two Minds: 1+1 > 2

One of the primary benefits of pair programming is the enhanced knowledge sharing that occurs when two developers collaborate closely. This collaboration helps in various ways:

  • Knowledge Sharing: Both programmers continuously learn from each other, sharing tips, tricks, and best practices.
  • Getting Unstuck: When one programmer encounters a roadblock, the other can often help find a solution, reducing downtime.
  • Onboarding: New team members can quickly get up to speed with the help of experienced colleagues.
  • Combining Tactical and Strategic Thinking: Pairing allows one programmer to focus on the immediate coding tasks (tactical) while the other considers the broader design and architectural implications (strategic).

Maintaining Flow

Flow is crucial in programming, and pair programming helps in maintaining it by:

  • Keeping Each Other Focused: The presence of a partner helps maintain concentration and reduce distractions.
  • Keeping Team’s Work-In-Process (WIP) Low: By working together, pairs can efficiently complete tasks, preventing the build-up of unfinished work.

Avoiding Waste

Pairing can mitigate several of the "7 wastes of software development" as described by Mary and Tom Poppendieck:

  • Partially Done Work: Ensuring tasks are completed efficiently and effectively.
  • Extra Features: Avoiding the implementation of unnecessary features by maintaining focus on current requirements.
  • Relearning: Reducing the need to revisit and relearn parts of the code due to continuous knowledge transfer.
  • Handoffs: Minimizing delays caused by transferring tasks between team members.
  • Delays: Accelerating the development process through real-time collaboration.
  • Task Switching: Maintaining focus on the current task, reducing the inefficiencies caused by switching between tasks.
  • Defects: Early detection and correction of errors through continuous review and feedback.

Enabling Continuous Integration

Pair programming supports continuous integration by:

  • Code Review On-the-Go: Continuous peer review ensures code quality and facilitates just-in-time integration. No need to use pull requests and long review cycles to get feedback.
  • Fostering Collective Code Ownership: Everyone understands the codebase, leading to better collaboration and fewer silos.
  • Frequent Integration Practices: Enables practices like trunk-based development, where developers integrate their work multiple times a day.

Implement pair programming in your team

Transitioning to pair programming requires a cultural shift and a commitment to the practice. Here are some tips to get started:

  • Start small: Introduce pair programming gradually. Begin with critical projects or complex tasks where the benefits are most evident.
  • Pair rotation: Rotate pairs regularly to ensure knowledge sharing across the entire team and to prevent burnout.
  • Provide training: Offer training sessions to help team members get comfortable with pair programming techniques and tools.
  • Create a supportive environment: Encourage a culture of mutual respect and continuous learning. Ensure that all team members understand the value of pair programming and are willing to embrace it.

More information

https://martinfowler.com/articles/on-pair-programming.html

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more