Earlier quoted context omitted.
Speaking as an employment _provider_ I fully agree nomad != remote. I'm actually hesitant to employ nomads if they are likely to move without warning to time zones that aren't convenient for the rest of the team. For example, one of the things that makes distributed teams work is to have a small number of very stable meeting times that remain invariant for long periods of time. The reason is that people need to struc…
I have been on remote teams with 2 different types of coordination. Meeting coordinated, which is usually centered around 1 or 2 weekly meetings when status updates and some amount of discussion of planning occurs. This model works best when a large portion of the team is on the same timezone or there is a physical office somewhere but isn't ideal for nomads or people that are permanently located in an inconvenient t…
I have run into practical problems with ad-hoc call when working across a lot of time zones (like 10 in our company). It's hard to slot in engineering ad-hoc meetings because the slots are limited to begin with and already used up with other things like talking to customers.
We definitely try to avoid burning people's time. Slack has been helpful for intermittent communication.