this post was submitted on 01 May 2025
1076 points (96.9% liked)

Comic Strips

16327 readers
2861 users here now

Comic Strips is a community for those who love comic stories.

The rules are simple:

Web of links

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -2 points 2 days ago (4 children)

27 Feb 2013 is unambiguous- regardless of where you're from or how you write your dates, you can't confuse 2013 for the month or day, you can't confuse Feb for a day or week, and if you can't figure 27 out, then we have bigger problems!

[–] [email protected] 24 points 2 days ago (2 children)

2013-02-27 is also unambiguous unless you’re aware of a country that uses year day month, is not?

[–] [email protected] 14 points 2 days ago

2013-02-03 though. Someone would fuck it up

[–] [email protected] 5 points 2 days ago* (last edited 2 days ago)

Which I was the justification used when my work decided to use 2025-May-01.

It’s close enough to the iso date that nobody will be confused but with that 1 extra layer of security blanket to separate months and days.

Of course, that does ruin sorting, so I think it was a bit silly, nobody has ever used yyyyddmm so it’s all a bit theoretical to me.

[–] [email protected] 2 points 1 day ago

I used to work for a company that agreed with you, well at least some clown in management did. Even though it was an Australian company, at least part of the problem was we had an office in Manila, and they speak "American English" which seemed to include the awful date system too. We dealt with a lot of files being issued to clients / received from vendors etc. Because the "official" system used those fucked up dates, everyone ran their own secondary sets of data folders in / out with everything done in ISO dates so you could actually sort it properly.

[–] [email protected] -1 points 2 days ago

27 Feb is no more or less ambiguous than 02-27. The problems are when you choose a proper example, like 03/02