Re: [extremeprogramming] Pairing styles

When I was first pair programming in my mid-20's, it was very exhausting because I wasn't used to being so engaged in my work.  It felt like 6 months of pairing was leveling me up with more experience than my previous 5 years of figuring out stuff on my own. Sustainable pace was a key practice to give me time to recover (my previous non-XP employer in the early 2000's, the unwritten rule was "any 80 hours per week I want").

Nowadays, when I'm coaching and helping others learn to pair effectively I take the back-seat driver role too. I'll admit that it's a little harder to see small fonts (maybe mobbing is helpful because we tend to use large TVs?).  I have suggested that people use a larger font size so I can see it from a farther distance, and the bonus benefit is that it will encourage them to write shorter methods and more readable code.

I also enjoy the older pairing style, I really like working with people 1:1. I find myself slowing down to teach people hotkeys, IDE features, command line tips, and improved local environment setup. This type of personal investment makes my pairing partner feel important which amps up their engagement and excitement for learning. This working style helps me get into and maintain flow by avoiding distractions (internal and external), and thinking out loud by clarifying my own thoughts with someone.  The added benefit is that it takes ego out of the code, so there is less personal attachment. My focus is to be the example of being a good navigator.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160154): https://groups.io/g/extremeprogramming/message/160154
Mute This Topic: https://groups.io/mt/39413621/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-