I worked on a small project at a previous job where we tried pair programming and it had mixed results.
We didn't do the "slide the keyboard and mouse back and forth" technique. Instead, we'd do shifts where one person developed on his machine for a while, while the other provided ideas/feedback/error-checking. Then, after a set time-period, we'd switch roles (after taking a break). It was actually physically exhausting for both of us (from what I've seen, a lot of developers need occasional distractions while working to keep their energy levels up) and I'm not certain it was more effective. I think we had fewer reported defects during testing (I can't recall for certain). It was only one test and might have worked better with more practice, but I don't think the company has used it since. Scott On Sat, Jun 25, 2011 at 1:58 AM, James Holmes <james.hol...@gmail.com>wrote: > > Anyone who wants to fix the problem of distracted programmers in the > office should try Pair Programming. > > http://www.extremeprogramming.org/rules/pair.html > > -- > WSS4CF - WS-Security framework for CF > http://wss4cf.riaforge.org/ > > > > -- ----------------------------------------- Scott Brady http://www.scottbrady.net/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345661 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
