4 ms·

I'm based in the UK but have a few clients in NYC. To be honest, translating from UTC to EST barely requires any thought at all for me now, and I always work t

I'm based in the UK but have a few clients in NYC. To be honest, translating from UTC to EST barely requires any thought at all for me now, and I always work to my clients' timezones, not mine - though, to be clear, I would usually phrase a meeting request like, "How about we have a call first thing in the morning your time, 9am EST?" (whilst in my head I'm thinking, "Yes, 2pm should fit nicely with my lunch plans"). Admittedly it does require more effort - and a little googling - when the clocks change; and I have definitely had issues with misunderstandings between iCal and Outlook over what timezone a meeting is in... which you'd think would be a solved problem in 2015, but seemingly not. Perhaps I've just been lucky, but the people I deal with have always been able to understand that a late afternoon meeting for them would mean a very late evening call for me - and if that's the best that they can do, they are always apologetic and appreciative of my being accommodating enough to do that.

Touche 12y ago
Yeah it's more of the constantly having to remind people that is annoying. You constantly have to be the person that forces a meeting to be rescheduled. The first remote job I had I worked at a startup in SF and typically everyone started work at 1 or 2pm. They'd schedule standups for 4:30 or 5:00. Of course I worked on the east coast and am a morning person. But what was I supposed to do (having just started)? Of course I'd attend the 8:00pm meetings (my time) even though I started work 12 hours earlier. It's been much easier in my experience where most people overlap at least 4 hours.