Re: "Winning" the pair programming discussion

> 
> > One complaint is pair programming is inefficent since you have 
less 
> > parallel task being worked on.  Three pairs can cannot not work 
on as 
> > many tasks in a single day as 6 programmers.
> 
> Note that this is far from obvious. Consider whether two people 
working
> together can carry more or fewer 200 pound bags of cement than the 
same two
> working alone.
> 

This is a VERY good metaphor.  I could also imagine that two people 
carrying cement all day might devise a simple tool or machine to help 
carry more faster.  I single person may not think of this.

> > You "might" add value 
> > with pairing when two people of equal level are paired, but 
pairing 
> > should NOT be considered when two novices are together or people 
of 
> > unequal skill.
> 

Well, of course the senior person would be slowed down having to 
explain everything to the junior person.  It would be become an 
exercise in frustrtion.  Or, of course, the junior person would never 
contribute since they have no clue what is going on and they are 
constantly overruled by the senior person.  Hey, ya know, it's human 
nature the experienced person intimates the inexperienced.
 
> The rules of collective code ownership are that any pair MAY 
improve any
> code at any time. They do not say that every pair WILL. They do not 
say
> that specialists won't mostly work in their area of specialization.
> 

I am of the opinion that it can only add value that any pair is 
capable of working on any part of the system.  




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

To unsubscribe from this group, send an email to:
[email protected]

 

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