Am I the only one here that hates mandatory 40 hour a week pair programming?

If you aren’t the one at the keyboard, it’s not that bad.

You are probably one of the only ones here that has this as a mandatory thing.

@AleCx04 it’s called “mentoring” elsewhere.

Management thought it was a great idea to improve code quality even though we all code review each other on the PRs. It's really hard for me to work like this. I'm more of a throw on headphones and focus kind of dev.

Pair programming makes sense for mentoring. When people need help I don't mind pairing but the mandatory 40 hours a week of pairing just does not make since to me. It seems like a very expensive efficiency bottleneck.

@Kahrazie how many hours are you putting in a week if 40 hours pair programming is mandatory? Or is every hour at work spent pair programming?

Whenever I have tried pair programming, my brain has turned to mush, and I become some gibbering twat who can't even type

Mandatory hours already feels wrong for a dev.

There have been studies on that. Pair programming kinda works with inexperienced programmers. With ones that are competent efficiency goes down almost 50% and code quality only increases slightly

@aspenscythe every hour is expected to be spent pair programming..

@Kahrazie that's insane. I think anything beyond an hour a day would make me want to kill my pair programming partner.