Yeah removing them is not a good idea. But they do need a nice global time complement for anything that is international such as broadcasts on the internet. I hate converting time zones to figure out when an event or broadcast starts.
That would be listed in plain terms on a website no conversion needed. I really only deal with individuals though, so they list their hours on teams and only some of them follow business hours anyways.
but regardless, imagine if you are meeting with 10 people all in different time zones. some in Arizona which doesn’t have DST. most don’t work 8-5 or whatever because thats old fashioned and sucks life from you. I’d rather know when you work on a single single clock. no confusion. it would take a couple months for everyone to adjust to their new clock and then everyone would be in sync.
yeah its a fantasy, but things are more connected every day. think of the boon for travelers and airlines.
Yeah I tend to agree, I schedule things with people across the world regularly and coordinating the time zones and business hours is a pain. If everyone used the same clock it would eliminate part of that issue.
Then a simple fix would be to not plan any meetings or calls for first or last thing in a day. Also, all work is expected due by first thing in the morning. So send that shit off as soon as you are done with it and its not a problem.
approximately 0 people think about it outside of programmers
It comes up all the time. Any time people are scheduling something between different time zones and run into trouble figuring out “is that your time or my time?” That’s an issue that would be resolved by not having time zones.
My point is you use UTC to plan international meetings but keep timezones for day to day stuff. Better yet with computers meeting planning software takes timezones into account.
When I do a when2meet with my colleagues everyone fills it in their local time and it’s fine, and then the calendar event is timezone aware as well so it’s completely a non issue.
It’ll never happen because approximately 0 people think about it outside of programmers.
Anyone who works with people in different time zones. Which is a lot more of us as we go remote.
Removed by mod
Yeah removing them is not a good idea. But they do need a nice global time complement for anything that is international such as broadcasts on the internet. I hate converting time zones to figure out when an event or broadcast starts.
That would be listed in plain terms on a website no conversion needed. I really only deal with individuals though, so they list their hours on teams and only some of them follow business hours anyways.
Removed by mod
8am is too early for anything….
but regardless, imagine if you are meeting with 10 people all in different time zones. some in Arizona which doesn’t have DST. most don’t work 8-5 or whatever because thats old fashioned and sucks life from you. I’d rather know when you work on a single single clock. no confusion. it would take a couple months for everyone to adjust to their new clock and then everyone would be in sync. yeah its a fantasy, but things are more connected every day. think of the boon for travelers and airlines.
Yeah I tend to agree, I schedule things with people across the world regularly and coordinating the time zones and business hours is a pain. If everyone used the same clock it would eliminate part of that issue.
Removed by mod
I think that it’s harder to all be in the same time zone. You then have to remember each zone’s working hours instead of the offset from your time.
I don’t see how it’s easier to get rid of time zones.
Yeah, when someone now says I get up at 05:00, we all know that’s early.
Getting rid of time zones would remove a lot of context to conversations.
If someone is getting up at 16:00, the others in the conversation would have no idea if that’s late or early, same goes for working hours.
Then a simple fix would be to not plan any meetings or calls for first or last thing in a day. Also, all work is expected due by first thing in the morning. So send that shit off as soon as you are done with it and its not a problem.
The Navy and Air-Force use of Zulu time would disagree with this statement.
It comes up all the time. Any time people are scheduling something between different time zones and run into trouble figuring out “is that your time or my time?” That’s an issue that would be resolved by not having time zones.
Just use UTC then.
Yes, that’s the idea.
My point is you use UTC to plan international meetings but keep timezones for day to day stuff. Better yet with computers meeting planning software takes timezones into account.
When I do a when2meet with my colleagues everyone fills it in their local time and it’s fine, and then the calendar event is timezone aware as well so it’s completely a non issue.