I found myself having to allocate mental bandwidth to my environment to allow for the possibility of being interrupted by others, so I ended up both less productive and more tired.
I find that the fact that I rarely get stuck for long and the mistakes I make tend to get caught more quickly makes pairing vastly more productive in practice.
The productivity isnt directly in the speed of code output but the compounded effect over time of it being higher quality - meaning vastly less time doing post hoc debugging, bugfixing, reworking code, etc.
At one company my (pairing) team routinely (and quietly) worked 9-3:30pm or 4pm while the surrounding teams worked overtime and still delivered way less. If you can nail it it really is almost unreasonably effective.
My thinking isn’t logical and it doesn’t use language internally. It’s difficult to explain but, due to mental disability I’m using my visual memory to do all of my information processing.
Let’s say it is not easy to describe a picture in words if things get complex.
It does a massive disservice to everybody involved, especially juniors who are never given the chance to prove themselves.
Funny enough, the two guys who pushed for it never did any pairing.
The CEO put the kibosh on it when he noticed the staff was not only unproductive but also massively unhappy.
But when I do with someone faster and that actually likes to discuss the implications, philosophy behind what we're doing it's amazing
I struggled a lot with impulse control but that’s managed well with meds. I often “zone out” when doing.. well pretty much anything that I’m not very interested in
On my own I can work about 2 hours on and 10 mins off, sometimes for 10+ hours total. If I have a 2 hour collab coding call, that’s about all I’ll do that’s productive that day. I’l literally have to spend the rest of that day mentally recovering from the stress of the call.