3 ms·
Probably the articles you've read and evangelists you've listened to were biased but it would seem your believe system is jaded by the fact that the one person
by majikandy 10y ago
Probably the articles you've read and evangelists you've listened to were biased but it would seem your believe system is jaded by the fact that the one person you think would be suited to pair programming is what you'd call a mediocre programmer. That's fine, but don't you think that is a little closed minded? You're evectively saying that you think the majority of pair programmers are just mediocre and aren't trying hard enough to solve problems on their own.
Forgetting the social side of things and forgetting the typing or the bugs, you must be be able to agree that two heads on one problem is better than one? Having another person to brainstorm some solutions to a problem with is faster and often gets a better solution that either of you would come up with alone?
- prodigal_erik 10y agoI find myself to be smarter and more capable of difficult design work when people nearby shut up and let me concentrate. How would two people constantly distracting each other always add up to one smart person?
- deleted 10y ago[deleted]
- khedoros 10y agoIt sounds like you operate how I usually do; the communication cost outweighs the benefits of collaboration, and it ends up being a tiring and frustrating experience. I've seen pair teams working correctly, though. Each of them bounces ideas off the other one, and they progress faster than either would've alone. It's like racing two algorithms against each other, each searching a different part of the problem space, and using the first result that's returned. It lets them move on to the next problem quicker. I don't usually do that very well, but I can't deny that if you've got the right pair of developers, it's a very powerful technique.