Despite living in the US my whole life, I don’t subscribe to the insane mm/dd/yy ordering, it’s the most ass backwards shit. That’s why I wrote 22 July. Not sure how you got 22nd month out of that when it’s unambiguous.
That part was unambiguous, and the month comment was clearly a joke; however, the very next line you write “22/7”. While you meant division, you accidentally wrote common date separator format, which WAS ambiguous and opened the door for the joke.
You could have written 22 ➗ 7 to get the effect you were aiming for ;).
Despite living in the US my whole life, I don’t subscribe to the insane mm/dd/yy ordering, it’s the most ass backwards shit. That’s why I wrote 22 July. Not sure how you got 22nd month out of that when it’s unambiguous.
Data Analyst background here. I prefer 20250722
digital artist here. i prefer 2025-07-22 for file sorting and it is easier to read
Technical drafter here,. Agree with you, ISO 8601 is the only right way
On this day 20250315, after many years of searching, I have finally found my people. The logical ones.
That is the mandate for all date structures that I can control.
Hello! I don’t intend to convince anyone one way is better than another, but I wanted to share why I like the mm/dd/yy format.
Simple reason, the number of possible integers increases as you go left to right.
12/31/9999
That’s all, got it out of my system. Thank you for reading.
That is pretty nice but it does not justify the inconvenience. Glad to have heard it :)
That part was unambiguous, and the month comment was clearly a joke; however, the very next line you write “22/7”. While you meant division, you accidentally wrote common date separator format, which WAS ambiguous and opened the door for the joke.
You could have written 22 ➗ 7 to get the effect you were aiming for ;).
It was a joke.