Why is pair programming an idea you should push in your team, and why sometimes you shouldn’t

Why is pair programming an idea you should push in your team, and why sometimes you shouldn’t?

I think every engineering manager should ask themselves this question. I push pair programming as often as possible during most of my coaching activities. This is a reflex I developed during my studies when I first learned pair programming. But I must confess that pair programming is not always possible.

As a manager, I also promote pair programming in my teams. By encouraging this practice, I foster a collaborative and productive environment.

This article will discuss the most frequent questions I get when talking about Pair Programming with other Engineering Managers. We are going to cover the following:

• (Only for those who don’t know) What is pair programming, and how does it work?

• What are the best advantages I have seen with pair programming?

• What is more productive between 2 developers in pair programming or two developers in parallel programming?

  • Two Developers Developing Independently with Pair Reviews

  • Pair Programming

  • What does the research say?

• Do we need to maintain code reviews when pair programming?