Putting the year first makes archiving easier. Your computer literally puts everything in order that way. Day first, and it will be sorted by the most frequently changing element.
Also year first allows you to timestamp your files, so they are sorted by what time you created them that day.
Sorting by day, at the end of the year you’ll have files from the first day of each month grouped together, then the second day, and so on. Still searchable, but not as orderly.
day should be first because it’s the one that changes the most often and we read left to right.
Putting the year first makes archiving easier. Your computer literally puts everything in order that way. Day first, and it will be sorted by the most frequently changing element.
Also year first allows you to timestamp your files, so they are sorted by what time you created them that day.
Sorting by day, at the end of the year you’ll have files from the first day of each month grouped together, then the second day, and so on. Still searchable, but not as orderly.
yea but I was talking in the context of a clock. for the uses you described YYYY MM DD is obviously better
People be hatin but I agree. in instances where the only goal is for a human to read the date, dd-mm-yyyy or even dd mmm(m) yyyy are better UX.
Next you’re going to suggest that 2000 should come immediately after 1000 (instead of 1001) because we read left-to-right.
I agree.
deleted by creator
use YYYY MM DD in the backend then.