Re:I Love Pair-Programming
by jrockway on Saturday February 21, 2009 @08:59PM
(#490296)
I found it useful when everyone else on my team was incompetent. Sitting down with them at least prevented them from going off and doing negative work all day. The result was pretty consistent output from the team, which is what companies aim for. It was less productive than firing the incompetent people and letting me do their work instead, however. (Incidentally, this makes it sound like I didn't get along with my coworkers, which was not at all true. After we started pairing, we all got along too well, and started wasting the entire day socializing instead of programming. Oops.)
Anyway, now that I don't have coworkers like this, I find it's easier to go off on my own. I also don't find it particularly useful to write a failing test and make it pass, I tend to alternate between big batches of code, a batch of passing tests, some todo tests, and then making that all work again.
YMMV, but you have to keep in mind that things like XP, Scrum, Agile, TDD, etc. are designed to make big groups do things in a consistent amount of time, so that the code works reasonably well and it is delivered in a predictable amount of time.
It is not necessarily a good way to do things if you are a good programmer. (Strict rules are for robots, not artists.)
Anyway, now that I don't have coworkers like this, I find it's easier to go off on my own. I also don't find it particularly useful to write a failing test and make it pass, I tend to alternate between big batches of code, a batch of passing tests, some todo tests, and then making that all work again.
YMMV, but you have to keep in mind that things like XP, Scrum, Agile, TDD, etc. are designed to make big groups do things in a consistent amount of time, so that the code works reasonably well and it is delivered in a predictable amount of time.
It is not necessarily a good way to do things if you are a good programmer. (Strict rules are for robots, not artists.)