Do the screens display the same content, and do the input devices control the same cursor? I find this 2-desk pair programming a curious arrangement.
Exactly, one monitor is an iMac the other is a thunderbolt display. The display just mirrors the iMac. We each have our own keyboard and mouse which controls a single cursor. The monitors face opposite each other so we are sitting (almost) directly face to face so talking to each other is natural with minimal turning, which would occur if you sat next to each other.
Interesting. I have a feeling this would drive me insane in the long run. Is there a particular problem you're attacking with this arrangement? Did you try a different approach before that didn't work so well?
Re:Pair Programming Considered Harmful?
by dustineichler on Saturday March 03, 2012 @04:20PM
(#3661162)
I'm glad you said that, but setups like yours are the exception not the rule. Last I was there, PL has the same. I'd mostly agree too it's a rewarding experience, but it needs to do done right. If you half ass the setup, it gets frustrating quickly.
Agreed. We started the project at Pivotal so that is where we got the setup, and I agree that it makes a huge difference.
It's a shame more companies don't implement pairing correctly. The extra grand (less if you don't go with an apple display) for the monitor is a small price for the results you get.
Re:Pair Programming Considered Harmful?
by dustineichler on Tuesday March 06, 2012 @03:19PM
(#3672668)
They're known for distilling culture and values on clients. It's apart of their high value-added proposition i think. e.g. - best practices.
We pair with 2 monitors, 2 keyboards, and 2 mice facing each other with our own desks which I feel gives each person in the pair enough privacy and space to make us both very comfortable.
Is pairing intense? Yep. Is it worth it? Absolutely in my mind. The high quality of the code and the productivity is well worth it.