4 ms·
> they can spend all night ruining your day before you even start work. Or they can be saving your service in emergency while you stay in bed. I'm not sure why
by viraptor 4y ago
> they can spend all night ruining your day before you even start work.
Or they can be saving your service in emergency while you stay in bed. I'm not sure why you'd expect a different time zone to mean lower skills than yours.
- yarg 4y agoI'm not - I'm saying that when it's a factor it's a big problem. I've dealt with entire offices of people that were problematic - you could tell when they came in, because builds broke universally in the next half an hour. And that was right at the end of the day. From half four 'till half five I spent my time fucking about rolling back commits and sending emails around the world to tell people to sort their shit out. Yes, there're regions where that's not a problem - the guys in our Poland office had their shit together, but it's not universal.
- viraptor 4y agoThat sounds like a management issue. You've got people being counterproductive who were hired, given tasks/permissions at inappropriate skill level and are not being dealt with appropriately. That's really not related to time zone in any way. Sure, it impacts your situation temporarily, but you could experience the same thing from local people working night shift. Let's keep in mind where the responsibility for solving the situation long-term really is.
- detaro 4y agoThe only remote (to me) office I had to work with that I'd describe like that was in California. shrug
- bergie 4y agoYep. When I was working with a very geographically distributed team, I loved being able to file a bug in the end of the workday, and have a fix ready for deployment by the time I opened my laptop next morning.
- ElFitz 4y agoIt’s mostly a problem when the main purpose in hiring remotely is to aggressively save money.
- viraptor 4y agoYes, it's a problem with management rather than with the workers or the timezone.