I mean, that’s already kind of an issue in the sense of determining what day something happened when using a timezone.
I think timezones help give a sense of shared “day” in the sense of when the sun is roughly meant to rise and set. I also think we’re super used to them and I don’t expect my opinion to change our relationship with time.
That said, timezones are wildly inconsistent and often difficult to track. This goes doubly for places that practice daylight savings of some kind. I like the simplicity of ideas like UTC and stuff.
I’m a software engineer, and we have a product that depends a lot on recording the time that something happened. In the past, one engineer coded the on-device agent using local time, and later on, a different engineer coded the ETL server code using UTC. It’s a huge headache, made even worse by the fact that the infrastructure for that server is in local time for a different time zone.
With a more normalized UTC, I think my life would definitely be a lot easier.
I mean, that’s already kind of an issue in the sense of determining what day something happened when using a timezone.
I think timezones help give a sense of shared “day” in the sense of when the sun is roughly meant to rise and set. I also think we’re super used to them and I don’t expect my opinion to change our relationship with time.
That said, timezones are wildly inconsistent and often difficult to track. This goes doubly for places that practice daylight savings of some kind. I like the simplicity of ideas like UTC and stuff.
I’m a software engineer, and we have a product that depends a lot on recording the time that something happened. In the past, one engineer coded the on-device agent using local time, and later on, a different engineer coded the ETL server code using UTC. It’s a huge headache, made even worse by the fact that the infrastructure for that server is in local time for a different time zone.
With a more normalized UTC, I think my life would definitely be a lot easier.