The decades but gained popularity thanks to the Extreme Programming XP methodology which was formalized by Kent Beck in the book Extreme Programming Explained: Embrace Change. There are several pair programming techniques each with different assumptions. Generally speaking it involves the cooperation of two programmers sharing one workstation working together to solve a given programming problem. The programmer currently writing the code is the socalled driver the second is the navigator also called the observer he also actively participates in the creative process but focuses more on the general direction and on continuous verification of the code written by the driver.
Benefits of pair programming My observations show that programmers working in pairs exert some kind of pressure on each other. They realize how valuable their partners' time is which is Email Marketing List why they want to use it as efficiently as possible. Depending on the technique used I'll talk about them later in the article the benefits of pair programming can be: better code quality and it is important that the person currently writing the code formulates his thoughts aloud this often allows you to solve a given problem even without significant interference from the other party easier sharing of domain knowledge between team members faster development of less experienced.
Programmers by pairing them with more experienced ones potentially greater resistance to external disruptions one person in the pair can always remain focused on the task while the other can for example participate in an external discussion with other team members. However it should be remembered that pair programming is difficult can be exhausting requires self-discipline and humility as well as the ability to give and give feedback. Often just knowing that someone will be looking over our shoulder for part of the day and judging what we do can disorganize our inner peace.
