Re: Pair Programming

So said  Ron Jeffries  on  12/20/2002 --------------------

>On Friday, December 20, 2002, at 3:55:55 PM, J. B. Rainsberger wrote:
>
>>>To look at this another way, pair-programming can at times, and more so
>>>for some people than others, be quite intense and tiring. We don't want
>to
>>>pair for 8 hours every day. Time alone to think is important.
>
>> 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.
>
>> Notice that that's not six solid hours of work, but a six-hour window
>during
>> which mostly pairing goes on.
>
>> I think that having a number in mind makes it easier to understand one
>aspect
>> of commitment we require a would-be XP organization to agree to; thereby
>> identifying yet one more area where we will be pressed for answers.
>
>How many hours a day can one write production code?

Indeed, Ron, but I'm looking for something I can take to management when they ask "just how much time would my team spend on this pairing stuff, anyhow?"


J. B. Rainsberger,
President, Diaspar Software Services
Let's write software that people understand.
http://www.diasparsoftware.com/
telephone: +1 416 791-8603
All correspondence (c) 2002 Diaspar Software Services.
If you want to use it, just ask; don't steal.




------------------------ 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/