Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

(Remote) Pair Programming

(Remote) Pair Programming as it was presented at 33rd Degree 4 charity at 13 October 2013, Krakow, Poland

Programming is often something that is done in solitude. Problem solving is something that often is done in a group. Programming is always about problem solving. It is therefore natural to do programming in groups. The group must not be too large and there must be at least two persons to make up a reasonable group. A pair turns out as the natural choice.

Pair programming is most efficient when the pair sits next to each other. This is not always possible. I will therefore show how to setup a remote pair programming session and then do some programming with a remote partner.

There is a myth that pair programming is twice as expensive as having one person solve each problem. The actual direct cost has been shown to be only 15% higher.

Thanks for directing me to the paper of Laurie Williams (slide #31). Was looking for it last week :-) Nevertheless Williams speaks of 15% less bugs (and not 50% less bugs as mentioned in slide 31). Williams shows that every project manager should trade in 15% less bugs for 15% overhead - paired developers are therefore much cheaper than independent developers