5 ms·

I found the article confusing because it begins by noting the deficiencies of studies on pair programming and then presenting data from... where exactly? I coul

I found the article confusing because it begins by noting the deficiencies of studies on pair programming and then presenting data from... where exactly? I couldn't tell. And then: It is obvious from table 3 that the best economic results do not come from pair programming but rather from hiring and using expert single programmers. Well... sure... of course, and good luck with that! Meanwhile, in the real world, while you're waiting for your expert programmers to submit their resumes to your company, pair programming is a great way to bring new/junior devs up to speed. In fact, I think that may be one of its greatest values. If you have two roughly equally skilled devs, it's possible that you'd be better served by working individually combined with good code reviews, though I don't think the article made much a case for that.

asynchronous13 13y ago
"Table 1 is extracted from a pair-programming calculator developed by the author." One could claim that the author made up numbers to support the author's argument. And hasn't pair programming been around at least since the 90's? doesn't seem that new to me.
- SomeCallMeTim 13y ago
  "Object Oriented" programming has been around since the '50s. [1] "Functional Programming" has as well. [2] And the "Waterfall" development model also has its roots in the 1950s. [3] "Extreme Programming" (1996, and a book in 1999) [4] was the first popular methodology to advocate "100% pair programming" as a major component. (I've read the book: They say that you have to use all of the practices, all the time, if you want "Extreme Programming" to work.) Point is that, depending on how old you are, the late '90s can qualify as "recent." [1] https://en.wikipedia.org/wiki/Object-oriented_programming#History https://en.wikipedia.org/wiki/Object-oriented_programming#Hi... [2] https://en.wikipedia.org/wiki/Functional_programming#History https://en.wikipedia.org/wiki/Functional_programming#History [3] https://en.wikipedia.org/wiki/Waterfall_model https://en.wikipedia.org/wiki/Waterfall_model [4] https://en.wikipedia.org/wiki/Extreme_Programming#History https://en.wikipedia.org/wiki/Extreme_Programming#History

asynchronous13 13y ago

"Table 1 is extracted from a pair-programming calculator developed by the author." One could claim that the author made up numbers to support the author's argument. And hasn't pair programming been around at least since the 90's? doesn't seem that new to me.

SomeCallMeTim 13y ago
"Object Oriented" programming has been around since the '50s. [1] "Functional Programming" has as well. [2] And the "Waterfall" development model also has its roots in the 1950s. [3] "Extreme Programming" (1996, and a book in 1999) [4] was the first popular methodology to advocate "100% pair programming" as a major component. (I've read the book: They say that you have to use all of the practices, all the time, if you want "Extreme Programming" to work.) Point is that, depending on how old you are, the late '90s can qualify as "recent." [1] https://en.wikipedia.org/wiki/Object-oriented_programming#History https://en.wikipedia.org/wiki/Object-oriented_programming#Hi... [2] https://en.wikipedia.org/wiki/Functional_programming#History https://en.wikipedia.org/wiki/Functional_programming#History [3] https://en.wikipedia.org/wiki/Waterfall_model https://en.wikipedia.org/wiki/Waterfall_model [4] https://en.wikipedia.org/wiki/Extreme_Programming#History https://en.wikipedia.org/wiki/Extreme_Programming#History