>??? wrote (in part): >If I could use an analogy here (I know it's always risky doing this, but I >feel it is valid), if we equate programming to painting (start with a blank >canvas, working to a goal that is only in our imagination at the moment), I >see the only real way a 'tag team' programming development can work is if >you have a basic 'paint by numbers' scenario, where purely technical skill >is involved, without imagination (or even understanding of where we will >end up). If, however, you need something with a bit of imagination, then >the rotating programmers would lead to something like a collaboration >between Picasso and Van Gough - fine individually but a mess when combined. And then there was Duke Ellington and Billy Strayhorn-- legend has it that one of the two would start composing/arranging while the other slept. When the active member of the team would get tired, they'd trade places, with the 'tag team' member picking up on the beat where the other one left off. Like a single mind in 2 bodies. So it -can- work. The team I've been working with for the past 9 years or so doesn't have quite that level of tag teaminess, but at times it's been close. --Paul E Musselman PaulMmn@ix.netcom.nospam.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.