4 ms·
You can usually find a way to make it work with any pair of timezones (e.g. North America and Europe, North America and Asia), but when you throw in a third dis
by cwzwarich 6y ago
You can usually find a way to make it work with any pair of timezones (e.g. North America and Europe, North America and Asia), but when you throw in a third distant timezone it becomes a huge pain.
At Mozilla, we had people working on the same project in North America, Western Europe, and Australasia. The meetings alternated between inconveniencing Europe / Australasia, but the additional latency of having all 3 timezones involved in decisions really slowed things down.
- jointpdf 6y agoI worked on a ~3 month remote project with people in timezones +6 and +12 hours ahead, which is arguably the worst configuration of timezones. Yet, we indeed found a way to make it work (and in fact I have some fond memories, though I doubt it was sustainable). The worst part was the project manager insisting on daily 7am standup calls (spoiler alert: I was not actually standing for these absurd calls).
- hn_throwaway_99 6y agoYes, I agree, you can "make it work", but not without a real negative cost to efficiency and employee morale. I don't know anyone that doesn't hate that "super early or super late" time span, and it just sucks for everyone. Over time I think many of your best employees will just refuse to work those kinds of hours indefinitely if they have other options. I specifically contrast that to when I worked with some excellent devs in Brazil who were only a couple hours off and the whole project and relationship was fantastic.