you are viewing a single comment's thread
view the rest of the comments
[–] 47 points 1 year ago (11 children)

there isn't a 16th month you silly goose

  • source
  • hideshow 11 child comments
  • [–] -3 points 1 year ago (10 children)

    Bigger values first, like standard numbers. That's how it sits correctly using alphabetical order. MM/dd.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 35 points 1 year ago (7 children)

    So you use year/month/day right? Right!??

  • source
  • parent
  • hideshow 7 child comments
  • [–] 3 points 1 year ago (4 children)

    100%

    And I name all of my filenames by YYYYMMDD and then the relevant name. Vastly superior and naturally intuitive. I also accept DDMMYYYY but I'm in the US and it's not as intuitive for others around here

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 1 year ago (2 children)

    Your way is automatically sorted by date when sorting by name and that's just, oh , uhhjh nnnnnngggg ahh.

    Please excuse me as I change my pants

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago (1 child)

    Or — hear me out — or you could sort by name if you want to sort by name and sort by modification date if you want to sort by modification date – and get this – sort by creation date if you want to sort by creation date.

    No need to shove two pieces of information in the same field.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago

    But creation date and or modification date aren't always the dates I want to sort by, so I use the same convention yyyy-mm-dd_name for most of my filenames too. It works for me, shoving those pieces of information all up in there. Lovin some shovin.

  • source
  • parent