Did the software industry learn nothing from Y2K? Was it too long ago already for people to remember the mess we made for ourselves?
Saving two characters in a file name is not worth the hell you are leaving in your trail by shoving this nonsense in an obscure corner of production code that people are going to forget about until it’s too late.
Their grandchildren will be pissing on their graves over it.
I often wonder what files may outlive me.
People have kept old physical remnants. There are obviously famous examples but there are far more mediocre examples.
All the unique content I’ve created fits on a modestly sized hard drive so keeping it around would be trivial compared to maintaining all those physical remnants.
And you assume that changes to filesystems, new filesystems being created or other such things won’t at some point create a edge case that creates a problem?
When you could just be safe? Sounds stupid as fuck to me to blindly trust nothing will happen to create problems.
I understand you feel very strongly about four digit years, but I really don’t see any situation that I couldn’t sort out with a simple script.
Usually I don’t put dates in file names in the first place, but when I do I use the UTC timestamp; a date without a timezone is inherently fuzzy, and it’s easier to compare and differentiate numerical times.
If someone used two digit years in their naming convention I wouldn’t even blink, let alone get the woodchipper, life is too short to get angry over stuff like that.
Did the software industry learn nothing from Y2K? Was it too long ago already for people to remember the mess we made for ourselves?
Saving two characters in a file name is not worth the hell you are leaving in your trail by shoving this nonsense in an obscure corner of production code that people are going to forget about until it’s too late.
Their grandchildren will be pissing on their graves over it.
I often wonder what files may outlive me.
People have kept old physical remnants. There are obviously famous examples but there are far more mediocre examples.
All the unique content I’ve created fits on a modestly sized hard drive so keeping it around would be trivial compared to maintaining all those physical remnants.
It’s just a filename, calm down. The created by date is tracked by the file system and the repo.
And you assume that changes to filesystems, new filesystems being created or other such things won’t at some point create a edge case that creates a problem?
When you could just be safe? Sounds stupid as fuck to me to blindly trust nothing will happen to create problems.
They’ve never had to recover a hard drive. It’s okay, they’ll learn the hard way.
I understand you feel very strongly about four digit years, but I really don’t see any situation that I couldn’t sort out with a simple script.
Usually I don’t put dates in file names in the first place, but when I do I use the UTC timestamp; a date without a timezone is inherently fuzzy, and it’s easier to compare and differentiate numerical times.
If someone used two digit years in their naming convention I wouldn’t even blink, let alone get the woodchipper, life is too short to get angry over stuff like that.
Until people start applying the same logic everywhere for consistency, not just in file names.