For other people their reference we're talking about https://about.gitlab.com/company/culture/all-remote/#disadva...
We try to prevent meetings as much as possible in GitLab by working async but I agree it is a huge problem, especially for the people in APEC.
Re:Why aren’t more companies remote-first?
by Aeolun on Wednesday June 05, 2019 @12:09PM
(#20105834)
The problem from my perspective is that there is just too many people working in the US and Europe, so APEC members always end up being the ones to accommodate (not necessarily of course, but it is most practical).
Re:Why aren’t more companies remote-first?
by shrimpx on Wednesday June 05, 2019 @11:41AM
(#20105532)
You can't really avoid this in a company with global presence. Forget the whole "remote" thing. If your company has an office in SF and one in Tokyo, people in the two offices will have to sync sometimes. That's a fact.
Re:Why aren’t more companies remote-first?
by ShakataGaNai on Wednesday June 05, 2019 @03:30PM
(#20108247)
That has nothing to do with being a remote company. It has everything to do with being a company that has people in more than one location. Most companies (especially in tech) beyond a few hundred employees have multiple locations - sometimes those locations are similar timezones (ex: SF & Seattle), but often they are very not the same.
In my case, my company has offices in San Francisco and Eastern Europe. 10 hours apart. Meetings at 8am for me are 6pm for them. So basically everyone has to compromise somewhat. As long as you go into things with understanding that this is the case, it's not that bad - especially if there is flexibility.
If you're working west coast USA to India (a common occurrence), it's 12.5 hours difference.
_Team members in different time zones may have to compromise on meeting times._
There is almost _nothing_ worse than this trap, especially if even a small majority of your team is in an inconvenient timezone, daily "standup" at 6:30am? ompany meeting at 1:30am here and there? You can keep it.