time zones

Midnight is a Confusing Choice for Scheduling

by

Midnight is a poor choice for scheduling anything. Midnight belongs to tomorrow. It’s 0000 on the clock, which is the beginning of the next day. That’s not how humans think, though, because tomorrow is after we wake up! A great example is a statement like “proposals are due by midnight on April 15.” What you actually said: proposals aren’t welcome after April 14. What you probably meant: you want the proposals before the date is April 16. There’s a 24 hour difference there, and if you enforce the deadline accurately people are going to complain because they were all thinking the second thing (before April 16). Similarly, this is a problem in change notices and customer communications. When you say …

Read More

Who Cares About Time Zones Anyway?

by

If you think you have a thankless job you should think about Arthur David Olson and Paul Eggert. Heck, it’s not even a paying job for them. They’re volunteers. Perhaps even masochists. What do they do? They maintain the time zone database (“zoneinfo”) for all of the computing world. And while residents of a particular country have to put up with just the general stupidity of their own politicians, these guys have to put up with all the stupidity of all politicians, across the Earth. Every time a politician in Russia, or Cameroon, or Indiana thinks it’d be a good idea to screw with the clocks these guys update and redistribute their database[0]. Vendors pick up the update and send …

Read More