• ILaughBecauseFunny@feddit.dk
    link
    fedilink
    arrow-up
    0
    ·
    7 days ago

    Issue: there are 27 different ways of writing a date.

    Engineers: We most make a common standard that is unambiguous, easy to understand and can replace all of these.

    Issue: there are 28 different ways of writing a date.

    Joke aside, I really think the iso standard for dates is the superior one!

    • m_f@discuss.online
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 days ago

      Do you mean the post titles? I’ve been using the same format as was used since before I took over posting, but if people want ISO format that works for me

  • driving_crooner@lemmy.eco.br
    link
    fedilink
    arrow-up
    0
    ·
    7 days ago

    In the last company I work for, the department was created from zero, and my boss just let me take all the technical decisions so from the begging everything was wrote in ISO-8601. When I left it was just the way it was, if you try to use any other date format anywhere something is going to give you an error.

  • jaxxed@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    7 days ago

    I was going to comain until I realized that the fprmat is the one that I prefer.

  • essteeyou@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    8 days ago

    My goodness, some of the comments in here must come from people who thought that those writing the standard were morons who did no research.

    • Katana314@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 days ago

      I don’t think they’re morons…just slaves to convention and compatibility. Not many ways to get away from that and justify it.

  • Guidy@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    8 days ago

    This format can fuck off. I prefer the unambiguous format 2FEB2013.

    Checkmate, date snobs.

    And yes, nations are free to use their appropriate abbreviations for the months.

    • TechGuy@discuss.online
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      8 days ago

      10:13pm or 8:13pm? I can see how this is confusing… perhaps another cartoon with more guidance might be needed.

      Personally I like date time groups: 272013 Feb 2013

    • brsrklf@jlai.lu
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      8 days ago

      So, assuming you got the time wrong and meant you could confuse year and time of day, ISO also puts time after date.

      2025-05-01T18:18:03Z

      Which makes sense. Higher unit to lower unit.

  • JackbyDev@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 days ago

    I feel like YYYYMMDD (without dashes) might be a format in ISO 8601, but I’m fully expecting to be corrected soon. But I didn’t say think, I said feel. YYYYMMDD has a similar vibe to YYYY-MM-DD, ya feel me?

    • compostgoblin@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 days ago

      Nope, you are correct! From the Wikipedia page, which cites the standards document:

      • Representations can be done in one of two formats – a basic format with a minimal number of separators or an extended formatwith separators added to enhance human readability. The standard notes that “The basic format should be avoided in plain text.” The separator used between date values (year, month, week, and day) is the hyphen, while the colon is used as the separator between time values (hours, minutes, and seconds). For example, the 6th day of the 1st month of the year 2009 may be written as “2009-01-06” in the extended format or as “20090106” in the basic format without ambiguity.