4 ms·
At TIM Group, I've followed the advice in your last sentence by hiring the very best developers I could possibly find and imposing minimal "management overhead"
by squirrel 15y ago
At TIM Group, I've followed the advice in your last sentence by hiring the very best developers I could possibly find and imposing minimal "management overhead". Interestingly, at some point they tried pairing, and decided it made them much _more_ productive; they continue to use it extensively even though it is not at all required (these days it is a cultural norm, but not dictated practise).
Just a single experience - a proper academic study would be very interesting if someone could manage it - but it doesn't seem to match your theory.
- mattiask 15y agoI'm sure there are developer pairings and scenarios where pair programming indeed would be beneficial. The point is that in your case the developers where free to themselves test and evaluate it's efficiency and then chose whether to use it. If that's the case then of course you should go with pair programming. That's different however from mandating pair programming where they'd have to use it whether or not it fitted them personally or that the pairing worked out. My point is not as much about specific practices but rather about mandatory ones.