• mkwarman@lemmy.world
    link
    fedilink
    arrow-up
    102
    ·
    2 years ago

    I’m definitely in the “for almost everything” camp. It’s less ambiguous especially when you consider the DD/MM vs MM/DD nonsense between US dates vs elsewhere. Pretty much the only time I don’t use ISO-8601 is when I’m using non-numeric month names like when saying a date out loud.

    • Dr. Wesker@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      Yeah, it’s pretty much everything for me too. The biggest exception being when UI is involved and a longhand date format would be more friendly.

    • usualsuspect191@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      In Canada we use MM/DD and DD/MM so you never quite know which it is! There’s an expense spreadsheet I fill out for work that uses one format in one place and the other format in another…

  • realbaconator@lemmy.world
    link
    fedilink
    arrow-up
    48
    ·
    2 years ago

    ISO 8601 gang. You’d never want to describe dates that way but for file management the convenience is massive.

  • TeckFire@lemmy.world
    link
    fedilink
    English
    arrow-up
    37
    ·
    2 years ago

    Upvoted because I appreciate the exposure for this dating method, but I personally use it for everything. Much clearer for a lot of reasons IMO. Biggest to smallest pretty much always makes the most sense.

    • Zink@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      I do too, even in notes at work or handwritten stuff at home. I don’t always need to be reminded of the year first, but sometimes it becomes important on older stuff.

      Plus when you’re in the US and work with people from Europe, the unambiguous ordering of month and day is a nice safeguard against silly misunderstandings.

  • cerberus@lemmy.world
    link
    fedilink
    English
    arrow-up
    27
    ·
    2 years ago

    ISO 8601 is amazing for data storage and standardizing the date.

    Display purposes sure, whatever you feel like

    But goddammit if you don’t use ISO 8601 to store dates, I will find you, and I will standardize your code.

    • snek_boi@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      2 years ago

      I actually need to standardize my code. I’ve got “learning F2” as something I want to do soon. The goal: use the exif data of my pictures to create [date in ISO 8601] - [original filename].[original file type termination]

      So a picture taken the third of march 2022 titled “asdf.jpg” would become “2022-3-3 - asdf.jpg”

      Help? lol

      • Samsy@lemmy.mlOP
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        I did this in the past and I would search through my notes… If I had notes ffs.

        • snek_boi@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          2 years ago

          I’m using NixOS. Ext4 filesystem. As to language, I’m not entirely sure what you mean. If you refer to the character set in the filenames, I think there are no characters that deviate from the English alphabet, numbers, dashes, and underscores.

          • cerberus@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 years ago

            Oh ok so you’re more so working with folder structure etc, so bash for when you plug-in a card?

            I’m thinking in more programmatic terms, there’s definitely some bash scripting you can execute. Or just go balls out and write a service that executes on systemctl

  • SlopppyEngineer@discuss.tchncs.de
    link
    fedilink
    arrow-up
    19
    ·
    2 years ago

    YYYY-MM-DD for everything. My PC clock, my phone and even my handwritten notes all use that format.

    The only other acceptable format is military notation: DD MMM YYYY.

  • RedEye FlightControl@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 years ago

    I’m a systems guy. ISO8601 or die. Whomever decided to put the most significant digits at the end of MMDDYYYY can get fired. From a cannon. Into the sun.

  • Tekchip@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 years ago

    Lot of talk of numerics only. The problem there is knowing what format the information is in since clearly there are 3 possibilities. Without context and during certain parts of the month you’re hosed. Best to remove ambiguity and go with the alpha numeric format.

    DD MMM YY (or alternatively YYYY)

    11 Aug 2023

    Ambiguity gone.

      • thawed_caveman@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        Any date format can be unambiguous as long as it’s the one that everyone agrees on, and all date formats will be ambiguous as long as we have several in use.

        I kinda gave up, nowadays when i write a date to someone i specify the date format. Like i will send “01/05/2024 (DD/MM/YYYY)” because it’s the only way to be sure