You think timezones are annoying? Try handling metrics that use imperial and metric, need to be rounded to different precisions across a large system, and are sometimes recorded in a different unit than it's viewed in. Slap some floating point error on there, and you got yourself a fun time.

I spent all day working on bug where backend was categorizing 19.9999 as falling between <20, but frontend was rounding it to 20 and categorizing it as >=20.

Edit: just to be clear, I don’t really think this is more difficult than date/time. But it does remind me a lot of solving date/time issues.

Tom Scott's video is about to do the rounds again then

Reading the pytz time zone database is an insane and engaging read.

Nobody is ever going to solve that problem.

Would be better as 4,294,967,295 instead of -1.

The switch to winter time was last sunday, it's been a fun week at work so far.

underflow

Just wait until they have to deal with places that don't use full hours to adjust the time.