Pair programming

While reviewing, the observer also considers the "strategic" direction of the work, coming up with ideas for improvements and likely future problems to address.

This is intended to free the driver to focus all of their attention on the "tactical" aspects of completing the current task, using the observer as a safety net and guide.

Pair programming increases the man-hours required to deliver code compared to programmers working individually.

[3] Along with code development time, other factors like field support costs and quality assurance also figure into the return on investment.

[3] Pair programming allows programmers to examine their partner's code and provide feedback, which is necessary to increase their own ability to develop monitoring mechanisms for their own learning activities.

The empirical studies tend to examine the level of productivity and the quality of the code, while meta-analyses may focus on biases introduced by the process of testing and publishing.

However, it raised concerns that its findings may have been influenced by "signs of publication bias among published studies on pair programming."

[2] A manager would have to balance faster completion of the work and reduced testing and debugging time against the higher cost of coding.