4 ms·
We should all just be on GMT. In software development on Pacific time, I always feel bad for the guys offshore that have to stay up late at night to make our m
by Adutude 6y ago
We should all just be on GMT. In software development on Pacific time, I always feel bad for the guys offshore that have to stay up late at night to make our morning meetings. It sure would make things a lot more easy from a coding perspective.
But to the point DST only adds complexity to the already complex task of converting time to GMT and back so that you can synchronize events in different time-zones, I fully support this effort.
- dheera 6y agoI run my entire life in UTC and no daylight savings. All of my clocks and phones read UTC.
- mongol 6y agoNot following. What do you mean? Will he not need to stay up late if "all are on GMT"?
- gruez 6y agoObligatory: https://qntm.org/abolish https://qntm.org/abolish
- ghaff 6y agoGuess what. You're still going to have morning meetings relative to your local solar cycle and the offshore guys are still going to joining the call at a time that they're probably thinking about bed based on their local solar time.
- chowned 6y agoThis comes up on every single article about timezones. Humans need to know what time it is based on the solar day. If it's 5:00 AM for me and 5:00 AM in Sydney, I have no clue if anyone in Sydney is awake. Timezones are for humans, not computers.
- Kwpolska 6y agoThis makes no sense. Your morning meeting will be at 17:00 UTC (for example), but it will still be “morning” in the SV office, and “afternoon”/“multiple hours past sunset”/“go away I’m asleep” for your offshore team (wherever they may be located). Changing the digits our clocks represent will only simplify those clocks, but it won’t, it can’t, it shouldn’t change business hours to 9-17 UTC everywhere. Because why would half of the world sleep when it’s light outside? Just because Europeans set UTC as a time zone and 23 as the time to go to sleep?