I would guess that in Data Science some things would require you to use local timezone because they are dependent on the actual time of day, and some would require synchronization so use of UTC. Also, some timezones are way off the sunlight time and would skew the data that has dependency on daylight and not on hours
But dealing with timezone conversions and daylight savings is a pain. Like if you make a recurring task every day BASED on the user’s timezone, it’s annoying because of daylight savings
Data scientists hate time zones.
Every dev hates time zones but I wouldn’t say it’s the number 1 enemy
I would guess that in Data Science some things would require you to use local timezone because they are dependent on the actual time of day, and some would require synchronization so use of UTC. Also, some timezones are way off the sunlight time and would skew the data that has dependency on daylight and not on hours
We should invent standard computing time (SCT) or something and use that.
UTC
But dealing with timezone conversions and daylight savings is a pain. Like if you make a recurring task every day BASED on the user’s timezone, it’s annoying because of daylight savings
And name it Zulu Time because it sounds cool.
But are we summer or winter winds?