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.

[–] azi@mander.xyz 21 points 3 weeks ago

hey at least once your code is correct it'll stay that way. You won't have to deal with things like old and new versions of your program disagreeing on what time it was in Iran for the last month and a half of 1978

load more comments (9 replies)