There are a lot of challenges with it, but I’ll never get over the magic of working in a global organization where you can tag team a project literally around the clock in a mostly sustainable fashion.
-
-
There was a story, I think in
@StevenLevy's book *Insanely Great*, about a developer/designer at Apple who did this—in the same time zone—working on the original Macintosh. Designer did user tests in the morning, dev came in afternoon and worked late into the night. 24-hour cycleThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is one of the often-overlooked benefits of open source, too. 24-hour, ‘round the world collaboration.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
When it works it works suuuuuper well
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We do not yet have any extraplanetary remotes (but watch this space).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I feel like 4-5 hour TZ gaps are the ideal for that, since you get a decent amount of overlap for calls/interaction and some focussed hours with your team. Without working late/early

-
3 timezones: US West Coast -> Sydney/Singapore -> Dublin/London ~8 hour diffs, 3 oncall shifts, 100% English-speaking. 2 timezones: US East Coast -> Dublin/London (Off by 5) or Europe (Off by 6, <100% native English) 2 oncall shifts, 2-3 hours of overlap.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.