4 ms·
Okay, but in this situation you are the one that asked them for help with your code. There's no "interrupted productivity" here if you're already blocked and wa
by nightpool 4y ago
Okay, but in this situation you are the one that asked them for help with your code. There's no "interrupted productivity" here if you're already blocked and waiting for advice or help with something. And besides, if you spend 3-6 hours working on completely the wrong thing because you were "in the zone" and that misunderstanding could have been resolved with a 5 minute call, then the 5 minute call is worth it every single time.
- wheels 4y agoYou're assuming both people are working on the same thing. I'm assuming they're not. You're also assuming there's only one task the developer could be working on. That's a very rare scenario.
- nightpool 4y agoThe person you're replying to said "If you want my help with just about anything code related, that's a call. Screensharing is way easier for me to see what you are talking about, and it's much easier for us to be on the same page if we're both looking at the same thing." I think that's an entirely reasonable position. How does this depend on "If both people are working on the same thing"? If I'm trying to help you debug something, and it feels like pulling teeth when I know I could solve your problem with a 5 minute screen-share, I'm probably going to choose the 5-minute screenshare over the hour-and-a-half of 10 different messages spread out over random intervals. The GP said the exact same thing: It's also a massive peeve of mine when someone asks a question on messaging, refuses to have a call, and then proceeds to take forever getting back to me. It's one thing [if] I say something like "Try this, this, and this. Let me know what works" and then I can get back to my work. But if I'm trying to step you through something and you sometimes reply immediately, sometimes in 5 minutes, sometimes in a half hour, then you get to have calls whenever you want my help from then on.