• content_educator_94
    152·
    2 months ago

    I’m glad you get to define wrong for everyone else

    Also I got news for you

    There are a variety of formats that are thriving and in constant use all over the world that differ from what you consider correct

    (I’ve never encountered a date format nazi before, this is first contact for me.)

    • ayyy@sh.itjust.works
      51·
      2 months ago

      I’ve never encountered a date format nazi before, this is first contact for me.

      I guess you haven’t had the pleasure of working with many database administrators then ;)

      • Appoxo@lemmy.dbzer0.com
        3·
        2 months ago

        Human readable: Either ddmmyyyy or yyyymmdd
        Computer: yyyymmddhhmmss only.

        Imo the only wrong thing to do is mmddyyyy
        That 's just cursed. Like imperial system.

        • ayyy@sh.itjust.works
          1·
          2 months ago

          But how do you document which version of an hour it is when daylight savings time “falls back”? What about leap seconds? Also if there’s no time zone specified is it local? UTC? GMT? I could go on…

          • Appoxo@lemmy.dbzer0.com
            2·
            2 months ago

            I am not living in a country with multiple timezones
            I am not working in a multi-national company.

            Should I have to define timezones, I will say so (e.g. “Let’s meet at 13:00 (or 1pm) CEST”)

    • Steve@communick.newsEnglish
      25·
      2 months ago

      I’m glad you get to definite wrong for everyone else

      It’s not the boon it seems to be.

      There are a variety of formats that are thriving and in constant use all over the world that differ from what you consider correct

      I’m aware. That’s why it’s annoying to be the one who determines what’s wrong, nobody listens.