• ඞmir@lemmy.ml
      link
      fedilink
      arrow-up
      29
      ·
      8 个月前

      As a computer scientist, I’ve been doing this everywhere for over 10 years already. Be the change you want to see in the world.

      • Suite404@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        8 个月前

        I worked for a company that did their dates multiple ways and it was fucking impossible to know what date was what. It was super frustrating. I’d prefer this, but if you don’t, at least keep it consistent once you start.

        • ඞmir@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          8 个月前

          If a date starts with the year, everyone will know the thing after it is the month. I’ve never ever seen YYYY/DD/MM. That, to me, seems like it wouldn’t add additional confusion at least.

    • epicstove@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 个月前

      In my computer engineering course this is literally how we were told to write the date on our lab reports.

    • Oaksey@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      8 个月前

      For written format that is ideal but when talking about a date, say in two weeks time, saying the year is redundant.

    • easily3667@lemmus.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 个月前

      Because humans are not computers. That scheme makes sense when you are filling out things that are not nearby in time. For example, filling in your birth date on tax forms.

      Otherwise, humans don’t generally need the context of the year. The same is true of the month only if the context is clear (I’ll see you on the 20th implies the very next 20th). A year is much longer and most things are not planned out that far in advance. If they are, they often dont have precise dates in which case a month or even a quarter is more appropriate.

      Time is also one of those things where humans are so used to contextual processing that representing the full date adds overhead. 2025/4/20, 4/20/2025, 20/4/2025 all take more processing than “the 20th” or “next Sunday”.