Any on-going work gets a new version daily. I start the day by saving current work to a new file, with the date/time in the file name:
E.G. Project Name 2024-04-09_08-32.xls
Using date with 24hr/military time like this enables sorting, and makes clear when the file was updated. This is especially useful iyou have to share a doc with peers - you never question what version they’re looking at (can’t always use a version control system).
Yeah, also generally very helpful for documents from banks etc.
(That’s a personal pet peeve of mine when people don’t do it like YYYY-MM but e.g. 1-Jan-2024. Who wouldn’t love to have their documents sorted in a way that it starts with the first day of every month, then all the second days and so on …)
My computer’s filesystem stores several “date” metadata fields for each file, such as “date created” and “date modified”, so I don’t have to manually manage such things in the file name. I can simply sort by recently modified, recently created, etc.
And those can change - it’s a local file system reference.
Windows historically has been really bad about this.
I have thousands of files in windows where the created date is actually last modified date - because the local file system updates on copy/move, or it gets altered by email/transfer systems, etc.
Really, would I have come up with my own naming system if the last mod and create dates were effective?
I have thousands of photos where the file system create time is years different than the metadata create time (what the camera stamped).
Yeah, autosave is such a lifesaver, I enable it wherever I can, Blender, Krita, Inkscape, Scribus, Thunderbird, autosave it all! And do your backups!
I keep versioned files around too.
Any on-going work gets a new version daily. I start the day by saving current work to a new file, with the date/time in the file name:
E.G. Project Name 2024-04-09_08-32.xls
Using date with 24hr/military time like this enables sorting, and makes clear when the file was updated. This is especially useful iyou have to share a doc with peers - you never question what version they’re looking at (can’t always use a version control system).
Yeah, also generally very helpful for documents from banks etc.
(That’s a personal pet peeve of mine when people don’t do it like YYYY-MM but e.g. 1-Jan-2024. Who wouldn’t love to have their documents sorted in a way that it starts with the first day of every month, then all the second days and so on …)
https://joplinapp.org/ does this on it’s export files btw … 😓
My computer’s filesystem stores several “date” metadata fields for each file, such as “date created” and “date modified”, so I don’t have to manually manage such things in the file name. I can simply sort by recently modified, recently created, etc.
And those can change - it’s a local file system reference.
Windows historically has been really bad about this.
I have thousands of files in windows where the created date is actually last modified date - because the local file system updates on copy/move, or it gets altered by email/transfer systems, etc.
Really, would I have come up with my own naming system if the last mod and create dates were effective?
I have thousands of photos where the file system create time is years different than the metadata create time (what the camera stamped).
Just use ISO 8601, it’s pretty much designed for this.