Ask HN: I'm experiencing pair programming exhaustion, how best to cope with it?

Post by nramenta » Thu, Aug 23, 2018, 12:49 AM UTC

Post by xmklb » Thu, Aug 23, 2018, 3:14 AM UTC

adiusmus wrote: post #3

What is your experience?

Post by otras » Thu, Aug 23, 2018, 3:42 AM UTC

xmklb wrote: post #4

adiusmus wrote: post #3

What is your experience?

The company I work for is completely committed to pair programming, which means everyone does it a 100% of the time. It is fine to help you ramp up when you just joined, but after 4 months of non-stop pairing, it seems like it's just too much.

Post by captain_perl » Thu, Aug 23, 2018, 5:58 AM UTC

pensatoio wrote: post #5

xmklb wrote: post #4

Earlier quoted context omitted.

The company I work for is completely committed to pair programming, which means everyone does it a 100% of the time. It is fine to help you ramp up when you just joined, but after 4 months of non-stop pairing, it seems like it's just too much.

That’s ridiculous. Pairing 100% would seriously hamper productivity. You need time to withdraw into your mind and think through solutions. This is why code reviews were invented.

Post by pytyper2 » Thu, Aug 23, 2018, 11:00 AM UTC

otras wrote: post #6

xmklb wrote: post #4

Earlier quoted context omitted.

The company I work for is completely committed to pair programming, which means everyone does it a 100% of the time. It is fine to help you ramp up when you just joined, but after 4 months of non-stop pairing, it seems like it's just too much.

This is such an interesting approach. I’ve read about this at Pivotal, and it’s interesting to see how it’s described on their blog vs Glassdoor. I greatly enjoy working with another engineer to solve an especially tricky problem, but only pair programming seems like it would be exhausting. What do you like and dislike about it?