4 ms·
Many here pointed out time difference is a pain. What can we do to compensate over the effect of time difference? Can having a better communication or async wor
by bhu1st 3y ago
Many here pointed out time difference is a pain. What can we do to compensate over the effect of time difference? Can having a better communication or async work flow work?
- re-thc 3y ago> Can having a better communication or async work flow work? reply Definitely. Problem is forget about timezone or cultural differences. A lot of places complain enough about remote vs in-person. This just makes it 10x harder for those people to adapt.
- sundaeofshock 3y agoOne caveat here; I work on US West Coast hours. Obviously time-zone issues are not as dramatic for hiring managers in Europe or Australia. Having said that… I used to work with teams in Bangalore and Pune. My nightmare (which I lived too many times) was us finding an issue with the offshore team’s work on Friday morning. When that happened, I knew I wouldn’t see a fix until Tuesday morning at the earliest. There are no async workflows that can fix that problem. Honestly, the best way to deal with time-zone issues is to hire senior folks. You need folks that can operate independently and can solve problems. Folks who can come up with solutions so they can keep working; not people who put down the keyboard for the day when they run into an edge case that’s not defined in the spec. Here’s the thing: senior developers in India are expensive. Add your margin to their salary, and the rate you charge for people is going to come close to what I pay for a developer in LATAM. At that point, I’m better off paying for someone in Brazil (for example) so I don’t have to deal with the async headaches.