I know. I started using the format with periods back in the 90s, before I knew of the standard, and at this point doing it with periods is muscle memory. That’s not meant as an excuse, just an explanation. The excuse is laziness.
It’s a flexible standard. 2026-05-10T10:06:09.426792Z, 2026-05-10 10:06:09.426792Z, 2026-05-10 10:06:09.426792, and 2026-05-10 all conform to the standard.
I rather have somebody write their invoices at DD-MM-YYYY cause there is a bigger chance it will most likely not be an invoice from a North American company which notriously cannot make proper invoices and most software that actually scans and processes invoices is based on the European standaard DD-MM-YYYY or on ISO8601.
Were you mostly joking or is there a utility to this? Genuinely curious as someone that finds confusing things slightly more memorable in a really backwards way
Waiting for the ISO 8601 & 9001 gang to show up and promote YYYY-MM-DD.
Edit: That took seconds, a very punctual bunch.
Hello I’ve arrived
Whoo! ISO-8601 fan club!
YYYYMMDD, scrub out the excess fat!
I use periods. YYYY.MM.DD
https://m.xkcd.com/1179/
I know. I started using the format with periods back in the 90s, before I knew of the standard, and at this point doing it with periods is muscle memory. That’s not meant as an excuse, just an explanation. The excuse is laziness.
Best excuse
Same here but not in the 90s. Since discovering the standard I have switched though.
If only there were some international standards organization to make a decision for us!
I’m now imagining a child who must write
2026-05-10T10:06:09.426792Z
on all of their tests.They should also add a timezone since most of us don’t live at UTC zero timezones -> 2012-12-28T18:12:33+09:00
They did; the
Z
at the end denotes UTC.My point was not everyone is just at UTC zero but sure Z is also a timezone.
Most people communicate mostly with people in the same timezone’s, partially because most countries only have one timezone.
It’s a flexible standard.
2026-05-10T10:06:09.426792Z
,2026-05-10 10:06:09.426792Z
,2026-05-10 10:06:09.426792
, and2026-05-10
all conform to the standard.I’m doing my part!
ISO thirsty!
ISO 8601/RFC-3339 (Unix Epoch also acceptable) gang reporting in.
deleted by creator
It’s the only way that makes sense
Hello from Hungary ! We should also democratize the Surname GivenName format
Szia. We should indeed.
o7
Anyone that gives me a document or receipt or invoice with a date formatted DD-MM-YYYY should have a tire iron swung at their thighs
Multiple swings if they can’t decide on using DD-MM-YYYY or MM-DD-YYYY or DD-MM-YY or MM-DD-YY or YY-MM-DD or YY-DD-MM
I rather have somebody write their invoices at DD-MM-YYYY cause there is a bigger chance it will most likely not be an invoice from a North American company which notriously cannot make proper invoices and most software that actually scans and processes invoices is based on the European standaard DD-MM-YYYY or on ISO8601.
YYYY-MM-… well, ya know the deal…
sup
As a big ISO 8601 guy myself, I request explanation of this 9001 addition? Never heard of it till now and am optimistic
Quality Management Systems, unsure what it has to do with 8601, but guess the fanboy venn diagram overlaps
Seconded. Not coming up with much when trying to find out more about it.
DD-MM-YYYY-HH-MM-SS
Makes no sense!
I prefer the alphabetical date format
DD-HH-MM-SS-mm-yy
for maximum confusionWere you mostly joking or is there a utility to this? Genuinely curious as someone that finds confusing things slightly more memorable in a really backwards way
Yes I was joking, get a random timestamp in this format and you have no idea what it’s referring to.
DD:HH:MM:SS:mm:yy
is even better because it could be a MAC address.