But that's not what happens...
The article states:
>> So, while it feels like there’s a “halving” of developers by pairing them up, as one of the original pair programming studies put it: “The defect removal savings should more than offset the development cost increase.”
Development cost increase? No, that's not what happens...
If a department has, say 20 programmers and Management decides to implement Pair Programming, they don't go out and hire 20 more programmers... They pair the existing ones up into 10 pairs. Then they hold meeting as to why it isn't working.
As I grow older and (hopefully) wiser, it is getting harder and harder to just accept the implementation of every new idea that Management reads in "Management Boy" magazine weekly. I already work well with others, shower daily and I am almost always minty fresh. Just let me do my work.
Can I get an "Amen!"
Biting the hand that feeds IT
