DD.MM.YYYY is the only sensible way, but I deliberately went with a date that could be read both ways. I’d wager the potato salad would be sentient in both timespans anyway.
Personally, I prefer YYYY/MM/DD. However, many non-programmers aren’t aware of this format, so when I mention that date format, they often think I’m making it up.
YYYY/MM/DD is good for archives since year is more important on archives but on everyday use DD/MM/YYYY is more convenient since most of the time you only want to know the day and month.
The reason YYYY/MM/DD is good from the point of view of programmers is because the natural “time” order corresponds to the lexicographical (alphabetical) order on strings if you use this format.
The reason I prefer YYYY/MM/DD is because it’s a nice compromise between the Europeans’ desire to see a date that is in a consistent order, and the Americans’ desire to see a date where the month comes before the date. That, and there’s no ambiguity.
Seriously, I’ve had to process dates like: 02/04/13
What does that mean? February 4th? April 2nd? If it were written 2013/MM/DD there would be no confusion.
It baffles me that even today many software engineers will still write the date as ??/??/YY, given all the problems we’ve seen so far with ambiguous dates.
The YYYY/MM/DD is painless to read, and painless to parse. (And it comes with the nice bonus that it alphabetizes nicely when sorted in ASCII-betical order.)
You’re lucky: my thirty-year-old leftovers tend to go on violent rampages when let out of their tupperware, leading to angry townsfolk showing up with torches, etc.
The REAL question remains: are you a DD.MM.YYYY our a MM.DD.YYYY?
Good point.
If the expiration date is February 10th, then the potato salad is surely bad.
But if it’s October 2nd, then there’s a chance it might still be okay.
DD.MM.YYYY is the only sensible way, but I deliberately went with a date that could be read both ways. I’d wager the potato salad would be sentient in both timespans anyway.
Personally, I prefer YYYY/MM/DD. However, many non-programmers aren’t aware of this format, so when I mention that date format, they often think I’m making it up.
YYYY/MM/DD is good for archives since year is more important on archives but on everyday use DD/MM/YYYY is more convenient since most of the time you only want to know the day and month.
The reason YYYY/MM/DD is good from the point of view of programmers is because the natural “time” order corresponds to the lexicographical (alphabetical) order on strings if you use this format.
The reason I prefer YYYY/MM/DD is because it’s a nice compromise between the Europeans’ desire to see a date that is in a consistent order, and the Americans’ desire to see a date where the month comes before the date. That, and there’s no ambiguity.
Seriously, I’ve had to process dates like: 02/04/13
What does that mean? February 4th? April 2nd? If it were written 2013/MM/DD there would be no confusion.
It baffles me that even today many software engineers will still write the date as ??/??/YY, given all the problems we’ve seen so far with ambiguous dates.
The YYYY/MM/DD is painless to read, and painless to parse. (And it comes with the nice bonus that it alphabetizes nicely when sorted in ASCII-betical order.)
He’s Norwegian.
You have the answer.
Wouldn’t it be weird if the refrigerator was made back in the 1990’s?
I’ve seen worse creatures growing in the crack of a woman’s ass!
(That’s why I had to get away! The wanted my side of the bed… and I ran away so they could have it!)
Only slightly older than me, that is.
Is that Krang from teenage mutant ninja turtles?
You’re lucky: my thirty-year-old leftovers tend to go on violent rampages when let out of their tupperware, leading to angry townsfolk showing up with torches, etc.
One day, jar of puréed tomatoes. One day… But you still have a decade or more to go. The jar of pickled cucumbers will have only the aged jars of jellied redcurrants to talk to for a couple of years, until it too will want to see the world.