Content deleted Content added
→Studies: added a comma for better reading; i don't think that changes the meaning intended in the sentence |
Citation bot (talk | contribs) Add: s2cid, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 110/2165 |
||
Line 6:
==Economics==
Pair programming increases the [[man-hour|person-hour]]s required to deliver code compared to programmers working individually.<ref name="ijhcs"/> However, the resulting code has fewer defects.<ref name="costs-benefits"/> Along with code development time, other factors like field support costs and quality assurance also figure in to the return on investment. Pair programming might theoretically offset these expenses by reducing defects in the programs.<ref name="costs-benefits">{{Cite journal|
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.{{citation needed|date=April 2022}}
Line 75:
|date=February 2007
| doi = 10.1109/TSE.2007.17
| s2cid = 9889035
| url = http://simula.no/research/se/publications/Arisholm.2006.2/simula_pdf_file
| access-date = 2008-07-21
Line 95 ⟶ 96:
==Remote pair programming==
'''Remote pair programming''', also known as '''virtual pair programming''' or '''distributed pair programming''', is pair programming in which the two programmers are in different locations,<ref>{{cite journal |last1=Flor |first1=Nick V. |title=Globally distributed software development and pair programming |journal=Communications of the ACM |volume=49 |issue=10 |year=2006 |pages=57–8 |doi=10.1145/1164394.1164421 |s2cid=8963421 }}</ref> working via a [[collaborative real-time editor]], shared desktop, or a remote pair programming [[Integrated development environment|IDE]] plugin. Remote pairing introduces difficulties not present in face-to-face pairing, such as extra delays for coordination, depending more on "heavyweight" task-tracking tools instead of "lightweight" ones like index cards, and loss of verbal communication resulting in confusion and conflicts over such things as who "has the keyboard".<ref name='jucs'>{{cite journal
| last = Schümmer
| first = Till
| |||