> Yo, you gotta tell me when you’re working. Sure, have core hours, and make them known. If I know someone won't be "at" work for the next 20 hours (part time

> Yo, you gotta tell me when you’re working. Sure, have core hours, and make them known. If I know someone won't be "at" work for the next 20 hours (part time, different timezone) I can factor that into how the teamwork will... Work. Is something on fire, and only a single person can put it out? A) that's sad B) sometimes happens anyway (and then you can try and fix A after the fire is out) C) depending on what's on fire, contracts etc - you can always call and wake someone up. But mostly it's just nice to know people's schedules - so one can plan work. Maybe there's some pair programming to be done (via shared screen session or whatever) - obviously try and schedule that when both parties are available... It's really not that different to chasing after a manager that's busy with meetings or a co-worker who's part time out of the office doing on-site consulting work. Even in a shared office, developers need to plan "deep" time when they have time to focus - or nothing will get done due interruptions. Just because someone is sitting right there does not mean they're "free" for a chat. They could be deep in the debugger chasing a bug.