A timezone is a constant (barring DST shenanigans) offset, which works for all the hours of the day. I can look at my watch here in Germany and I know that it’s 8:15 in New York right now. So I know that it’s still early in the day for my buddy Jeff.
In the same-time everywhere logic, I would need to remember specific times, like “people in New York usually start working at 15:00 and stop at 24:00”, which is just plain inefficient.
Again, how is remembering whatever the New York offset is from your own work hours any different than remembering their time zone? If you have a remote coworker in a different time zone do you not already think things like “they’re not at their desk until 10 so I can’t schedule anything with them before that”?
The inconvenience you’re describing already exists and doesn’t change, you’re just used to the current specifics.
A timezone is a constant (barring DST shenanigans) offset, which works for all the hours of the day. I can look at my watch here in Germany and I know that it’s 8:15 in New York right now. So I know that it’s still early in the day for my buddy Jeff.
In the same-time everywhere logic, I would need to remember specific times, like “people in New York usually start working at 15:00 and stop at 24:00”, which is just plain inefficient.
Again, how is remembering whatever the New York offset is from your own work hours any different than remembering their time zone? If you have a remote coworker in a different time zone do you not already think things like “they’re not at their desk until 10 so I can’t schedule anything with them before that”?
The inconvenience you’re describing already exists and doesn’t change, you’re just used to the current specifics.