I used to be the DST/Time Zone Messiah for a large software company. Meaning that I was responsible for making sure that certain time APIs worked. It was supposed to be simple. All you have to do is lookup the delta and then apply it to GMT right? It wasn't. All because of DST and Time Zones and the history associated with them.
Everyone wanted their documents to reflect the exact time that they were created. They also wanted to be able to calculate the exact time when something occurred in the past. I had headaches dealing with leap days, time zones, DST. I'd get all these bugs from people saying: "My files changed creation dates!"or "The calculation for [some lame historical event] isn't right!" The worst part was when I got some bug for a mail server client that was working on legacy hardware but needed to interface with our new stuff. Sigh.
I think I'm done complaining. Sometimes I miss working there. But when I see topics like these, I feel wonderful!
Slashdot Mirror
I used to be the DST/Time Zone Messiah for a large software company. Meaning that I was responsible for making sure that certain time APIs worked. It was supposed to be simple. All you have to do is lookup the delta and then apply it to GMT right? It wasn't. All because of DST and Time Zones and the history associated with them.
Everyone wanted their documents to reflect the exact time that they were created. They also wanted to be able to calculate the exact time when something occurred in the past. I had headaches dealing with leap days, time zones, DST. I'd get all these bugs from people saying: "My files changed creation dates!"or "The calculation for [some lame historical event] isn't right!" The worst part was when I got some bug for a mail server client that was working on legacy hardware but needed to interface with our new stuff. Sigh.
I think I'm done complaining. Sometimes I miss working there. But when I see topics like these, I feel wonderful!