(no title)
rpgwaiter | 11 months ago
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.
lurkshark|11 months ago
pydry|11 months ago
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. It is invisible over the space of one or two tickets, visible over weeks and overwhelming over months.
At one company my pairing team routinely (and quietly) worked 9-3:30pm or 4pm while the surrounding nonpairing teams worked overtime and still delivered way less. If you can nail it it really is almost unreasonably effective.
whstl|10 months ago
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.
darkwater|10 months ago
jim-jim-jim|11 months ago
It does a massive disservice to everybody involved, especially juniors who are never given the chance to prove themselves.
jfrbfbreudh|11 months ago
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.
criddell|10 months ago
dlivingston|11 months ago
yaomtc|11 months ago
rpgwaiter|11 months ago
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
unethical_ban|10 months ago
ErigmolCt|11 months ago