|
|
|
|
|
|
by thadeus_venture
5463 days ago
|
|
|
Different strokes for different folks i guess. I know a lot of people will be fans of this, but >we pair program to write all of our software. We work on Mac Pros with two keyboards and two monitors. We work in an open team room; no cubicles or private offices. No thanks, if I'm the developer. And if i wouldn't do it, why would i make my employees. |
|
|
When you're pair programming, you're not wearing headphones and "getting into the zone". You're openly collaborating, sharing thoughts, bouncing ideas, prototyping things on a whiteboard, and so on. Just like at a party, you subconsciously filter out the surrounding noise when you're talking to your pairing partner. An open office is perfectly fine for this. I didn't think it would be a good situation at first, either. :)
However, I personally do not enjoy pair programming. There's a few reasons why, but the big one is that it's mentally exhausting. Eight hours of engaging in conversation completely wipes me out even if it results in amazing code. I couldn't deal with it any more. To a lesser degree, I do not get the same sense of accomplishment from completing tasks when pair programming that I do from completing tasks by myself.
That said, if I ever run a company with a handful of programmers or more, I'm going to hire engineers who like pair programming.