Content deleted Content added
m Reverted edits by 90.243.227.10 (talk) (HG) (3.4.10) |
m some ref cleanup tags should be AFTER </ref>, replaced: {{self-published inline|date=April 2016}}</ref> → </ref>{{self-published inline|date=April 2016}} |
||
Line 8:
In addition to preventing mistakes as they are made, other intangible benefits may exist. For example, the courtesy of rejecting phone calls or other distractions while working together, taking fewer breaks at agreed-upon intervals, or shared breaks to return phone calls (but returning to work quickly since someone is waiting). One member of the team might have more focus and help drive or awaken the other if they lose focus, and that role might periodically change. One member might have knowledge of a topic or technique which the other does not, which might eliminate delays to find or test a solution, or allow for a better solution, thus effectively expanding the skill set, knowledge, and experience of a programmer as compared to working alone. Each of these intangible benefits, and many more, may be challenging to accurately measure, but can contribute to more efficient working hours.
==Design quality==
A system with two programmers possesses greater potential for the generation of more diverse solutions to problems for three reasons:
Line 106 ⟶ 107:
Tool support could be provided by:
* Whole-screen sharing software<ref>[http://blogs.pathf.com/agileajax/2007/09/pair-programmin.html Agile Ajax: Pair Programming with VNC<!-- Bot generated title -->] {{webarchive|url=https://web.archive.org/web/20080402003711/http://blogs.pathf.com/agileajax/2007/09/pair-programmin.html |date=2008-04-02 }}{{self-published source|date=April 2016}}</ref><ref>[http://weblogs.asp.net/jcogley/archive/2004/10/13/242117.aspx Pair Programming – The Ultimate Setup and the other options we tried. – Jonathan Cogley's Blog<!-- Bot generated title -->]</ref>{{self-published inline|date=April 2016}}
* [[Terminal multiplexer]]s
* Specialized distributed editing tools
| |||