Re: Another idiotic software idea
If I were a top-notch programmer, the very last thing I'd want was someone bugging me of reformatting my code.
Me too! Fortunately, pair programming is not like that at all. When I work along, I am a pretty good programmer. But I always produce better code when I pair.
There's an interesting rhythm when pairing. When I have the keyboard, I'm very focused on solving the problem that's before me, getting the syntax right, getting loop conditions correct, all the nitty gritty details of the problem at hand. At a certain point I have to stop and look forward and start plannning where the software needs to go. If I were alone, I would kick back a bit and start planning my next coding burst. But when I am pairing, my partner has been doing that already. He's been watching the code and making suggestions, but because he has not invested as much mental energy in the details, he can use his spare brain power for some longer range planning. When I slow down, he is ready for a turn at driving (i.e. having the keyboard). We switch and while he drives, it's my turn to take the longer view.
So, my solo programming sessions are a pattern of quick bursts of coding spaced by periods of reflection. But a pair programming session is more consistent, with the pairs switching between long-range and short-range planning as they go.
It takes practice to be a good pair programmer. The first time you try it, it will probably feel awkward. But give it some practice and its quite possible you will enjoy it more than you would expect up front.
Well, anyways, that's my experience.
Anybody live near Cincinnati that would like to pair with me?
