17 ms·
Man, I'd honestly find example 2 more stressful than example 1. Is pair programming really something that programmers find useful? Should I develop this skill m
by archagon 14y ago
Man, I'd honestly find example 2 more stressful than example 1. Is pair programming really something that programmers find useful? Should I develop this skill more? I've barely had to do it at all at my jobs, and when I have, it 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.
I guess I should read up on concurrency. :)
- 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.
- burntsushi 14y agoPair programming is really interesting. I've taken several courses where there was an optional pair programming portion, and after trying it a few times, I swore it off for good. I hated pair programming because every person I worked with just sat there (without interest). Which is just stupid. But recently, I did some pair programming with folks closer to my skill level, and it was much better. I wouldn't swear by it or anything, but we were both working through a really hard problem, and it was helpful to write code together. It was slower, but I felt like I absorbed the problem quicker. Also, one tip: plug in an extra keyboard. The driver is still the driver, but if the other chimes up and thinks of a better way to write a particular piece of code, it's easier to just let them instead of having them explain it to the driver or having to switch the keyboard over or something.