Editing Pair programming (section)

==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
|author2=Stephan Lukosch
| title = Understanding Tools and Practices for Distributed Pair Programming
| journal = [[Journal of Universal Computer Science]]
| volume = 15
| issue = 16
| pages = 3101–3125
|date=September 2009
| url = http://www.jucs.org/jucs_15_16/understanding_tools_and_practices/jucs_15_16_3101_3125_schuemmer.pdf
| access-date = 2010-04-30}}</ref>

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
* Audio chat programs or VoIP software could be helpful when the screen sharing software does not provide two-way audio capability. Use of headsets keep the programmers' hands free
* Cloud development environments
* Collaborative pair programming services