Contents
What challenges would you expect to arise during pair programming?
Challenges & common pitfalls
- Pair-programming is NOT the right tool for every task.
- Pair-programming is NOT right for everyone.
- Remote pair-programming.
- Lack of engagement.
- Silence.
- “Watch the Master”
- Loss of Confidence.
- Lack of code-ownership.
Does pair programming reduce the need for refactoring?
The refactoring of code is always part of coding, and therefore of pair programming. It’s easier to improve code when you have someone beside you because you can discuss approaches or the naming of things for example.
What is the benefit of pair programming?
Pair programming is an important technique for developing higher quality code, faster while also reducing risk and spreading knowledge in an organization. With pair programming, two software developers work on one computer, collaborating on the same design, algorithm, code, or test.
What do you need to know about pair programming?
Pair programming consists of two programmers sharing a single workstation (one screen, keyboard and mouse among the pair).
What makes a pair better than an individual developer?
improved resiliency of a pair to interruptions, compared to an individual developer: when one member of the pair must attend to an external prompt, the other can remains focused on the task and can assist in regaining focus afterwards
When did pair programming start in the agile movement?
However, the following timeline of verifiable sources does suggest that pair programming, in its modern form, has been around since well before the Agile movement:
Why are posterior studies so common in pair programming?
Posterior studies are more abundant and driven by the desire to “validate” pair programming after it had already gained popularity through Extreme Programming.