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.
And you can do a simple sort on the combined number and youve sorted by date.
ISO 8601 is always the correct way to format dates.
ISO 8601 gang. You’d never want to describe dates that way but for file management the convenience is massive.
I do. Anything I have to put a datecode on, always gets a stamp of YYYYMMDD.
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.
Nah, for everything.
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.
epoch not acceptable then?
I will agree it’s a valid storage but it has to be specified in ms
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
I did this in the past and I would search through my notes… If I had notes ffs.
Can you give more context, what are you using? Language / system / etc?
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.
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
There are two ways of writting dates: the “yyyy-mm-dd” one and the wrong one
better than the absolutely deranged MM/DD/YYYY and imo the best when it comes to international communication
/c/ISO8601
YYMMDD is how a start my file names. It’ll work great for another 75 years or so.
Found the guy who was born after the year 2000
Way off
I like yyyy-mm-dd and dd/mm/yyyy
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.
When I try to enter a date in excel and it formats it as numerical 424523 or some shit smh
Seeing as I do a lot of AV editing I use this format to keep track of Audio files I do production on. YYYYMMDD Filename Version. It’s often a case of working on a file and coming back to it weeks or months later, and in most cases there are multiple versions and revisions as I collaborate with my production partner.
It helps me keep track of the timeframe, what it is and which version so I can ensure rendered versions I’m using in other directories or as assets in other files are consistent and up to date.
The directories got quite messy and confusing initially until I adopted the ISO date format for this case.
in most cases there are multiple versions and revisions as I collaborate with my production partner.
Y’all MFs need version control.
