• moseschrute@lemmy.world
    link
    fedilink
    arrow-up
    51
    ·
    edit-2
    8 days ago

    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.

  • panda_abyss@lemmy.ca
    link
    fedilink
    arrow-up
    5
    ·
    8 days ago

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

    Nobody is ever going to solve that problem.

  • luciferofastora@feddit.org
    link
    fedilink
    arrow-up
    5
    ·
    8 days ago

    Oh damn, I forgot to check which of my scheduled tasks were set to UTC, which were set to local time and whether they adjust automatically and what schedule the upstream tasks by different teams run on again.

    Oh well, nobody cried about anything breaking yet, so I might be in the clear. For now.

    • humanspiral@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      8 days ago

      One of the worst things about having DST at all is that it is not standardized through world. North America has not switched yet, and people making these announcements make me think my phone is broken.