In every left to right language, the largest value numerical digits are on the left, smallest value digits are on the right.
The country doesn’t matter. Years are bigger than months. Months are bigger than days. If your country does anything other than YYYY*MM*DD, they’re doing numbers wrong.
But how do you document which version of an hour it is when daylight savings time “falls back”? What about leap seconds? Also if there’s no time zone specified is it local? UTC? GMT? I could go on…
In every left to right language, the largest value numerical digits are on the left, smallest value digits are on the right.
The country doesn’t matter. Years are bigger than months. Months are bigger than days. If your country does anything other than YYYY*MM*DD, they’re doing numbers wrong.
I’m glad you get to definite wrong for everyone else
Also I got news for you
There are a variety of formats that are thriving and in constant use all over the world that differ from what you consider correct
(I’ve never encountered a date format nazi before, this is first contact for me.)
I guess you haven’t had the pleasure of working with many database administrators then ;)
Human readable: Either ddmmyyyy or yyyymmdd
Computer: yyyymmddhhmmss only.
Imo the only wrong thing to do is mmddyyyy
That 's just cursed. Like imperial system.
But how do you document which version of an hour it is when daylight savings time “falls back”? What about leap seconds? Also if there’s no time zone specified is it local? UTC? GMT? I could go on…
I am not living in a country with multiple timezones
I am not working in a multi-national company.
Should I have to define timezones, I will say so (e.g. “Let’s meet at 13:00 (or 1pm) CEST”)
It’s not the boon it seems to be.
I’m aware. That’s why it’s annoying to be the one who determines right and wrong, nobody listens.
I don’t get the downvotes. Even if no country at all uses it, there is only one correct order of the numbers.
LOL