RE: Pair Programming

> -----Original Message-----
> From: J. B. Rainsberger [mailto:[email protected]]
> I certainly couldn't pair eight hours every day. I assumed 
> that the PP problem was being considered in the context of 
> not being able to pair even for (say) four hours every day. 
> An interesting question: how little pairing is too little, in 
> hours? I'll set the bar at about six.

This may be off of the topic of extreme customering. If so, somebody say so and we'll stop.

I don't think the bar metaphor is appropriate for reasons I'll explain in a moment. But if pressed to set a bar, I'd set it at 2 hours. To me, it's not worth sitting down to code if I cannot spend a couple hours. The context switching costs (which include the pre-coding design discussions) are too high for anything less than that.

Back to the bar of "n hours/day spent pairing" being the wrong metaphor: A more appropriate measure of commitment is "all production code written in pairs" (with some minor exceptions a team can agree to). Some teams and individuals have other non-coding duties that may keep them from coding for a couple days.

regards
andrew fuqua


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
extremecustomering-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/