3 ms·
> Is pair programming really something that programmers find useful? Some do. Some people swear by it. > Should I develop this skill more? Yes, definitely. T
by aaronbrethorst 14y ago
> Is pair programming really something that programmers find useful?
Some do. Some people swear by it.
> Should I develop this skill more?
Yes, definitely. Think of it as being a more social version of learning a new programming language or systems architecture.
> [I]t was difficult for me because I couldn't get into my usual flow. Even with an extra pair of eyes and hands, I felt like I was working at 50% efficiency.
It's definitely an acquired skill. If you think about it, though, if you're spending most of your time while programming engaged in typing, odds are you're probably doing something wrong (or working in a ridiculously verbose language ;)
- seanmcdirmid 14y ago> If you think about it, though, if you're spending most of your time while programming engaged in typing, odds are you're probably doing something wrong. He didn't say anything about typing. Pair programming is meant to be slower than alone programming, the extra eyes and ears actually slow you down because you have to reach consensus so often. Pair programming is about quality, not productivity.
- jtheory 14y agoAnd quality is in turn at least partly about productivity (i.e., it's usually faster to avoid the bug than to fix it after the fact).
- seanmcdirmid 14y agoIt really depends if you need the quality or not. Also consider Gabriel's "worse is better." Anyways, doing pair programming can be considered as another tradeoff (as you more than halve the productivity of your team); it shouldn't be valued as always a net positive.
- jtheory 14y agoYup; lots of variables to play with. As long as we're actively aware of the tradeoffs (and adjust approach as needed) it's all good. I don't personally find pair programming very useful most of the time, though I've done it now & then... though I do benefit from the half-way version, which is to occasionally talk through problems I'm working on with other developers (in detail, with code).
- seanmcdirmid 14y agoI personally benefit from the rubber duck approach, but I'm a researcher without so many people to talk to.