Re:Lessons Learned from the Book “Effective Remote Work” (2022)
by pydry on Monday January 02, 2023 @06:07AM
(#34216621)
I find that pair programming requires a high degree of psychological safety for people to try it and an even higher level for people to actually enjoy it.
I'm pretty sure that by default remote work with a low level of face time leads to lower levels of psychological safety.
Re:Lessons Learned from the Book “Effective Remote Work” (2022)
by gregwebs on Monday January 02, 2023 @06:18AM
(#34216703)
I use the term pair program very loosely- much like any work conversation but centered on code. In the past, these conversations tended to only happen asynchronously during code review, but now we are having them while work is in progress and for code review and it is a lot more productive for us than asynchronous.
Re:Lessons Learned from the Book “Effective Remote Work” (2022)
by theshrike79 on Monday January 02, 2023 @06:18AM
(#34216700)
I have seen pair programming in actual use exactly once. And it was a pair of dudes who had known each other since kindergarten and were roommates. They basically shared a brain.
I've tried it a few times and it's like trying to read the same physical book at the same time with someone who's a lot slower or faster reader.
Remote work has finally made it possible for me to pair program and otherwise work synchronously with others.
Rather than being forced to work in a distracting open office, I finally have a private office – something I have never had during my entire career working in offices.
In the past being in an open office environment meant that collaborating with someone always risked being rude- disrupting others with our conversation. This would sometimes be handled by using a meeting room, but this still isn’t as good as just both of us communicating from our offices.
For synchronous remote work It’s crucial to still work with people in similar time zones.