A recent discussion on the ALE LinkedIn group about pair programming made me remember a fun little event I lived recently. Read on for a true story about the power of pairing.
A couple of weeks ago I was at a client site and we had a meeting scheduled for 11 am. Shortly before the meeting I got an email notifying me that it will be delayed for 10 minutes.
What to do in the meantime? Even if my role in that assignment was to help a team adopt Kanban, I always try to get a glimpse at the code and see how clean it is. I find it often speaks louder than words. I decided to ask a developer (let’s call him Paul) to show me what he was working on. As it turns out, Paul was actually stuck with a problem and had been fighting with it for the last twenty minutes.
Much to my surprise, about five minutes into our exploration, without really understanding much of anything, something jumped at me. Hey, shouldn’t that “class=” be an “id=” ? I asked Paul. He looked at me silently, changed the code as I suggested and voila!, the bug was gone. As I stood up, I heard Paul say: Dude, we should do this more often!
With three minutes left, I walked to the coffee machine, poured myself a black coffee and slowly headed towards the meeting room.