I've noticed a lot of UK job applications use the American MM/DD/YYYY date format and some also say "resume" instead of CV. Does that annoy you if you're British?
It annoys me even though I'm still in the U.S.
Edit: For everyone saying CVs and resumes are different, that might be literally the case, but that is not how job applications are using them. I just went to this one:
The only correct format is from greatest to smallest: yyyy-mm-dd
This is, in my mind, verifiable by noting the way that lists are ordered when using this format. They are sequential. This isn’t true for either of the other formats.
Dates written in a numbers only format are not about matching the spoken language. You also would not say, "let's meet on twelve eleven twenty twentyfour."
In German and Swedish, "the twelft eleventh" would be totally fine. Beside this would be November 12th. The German way for the year would be twothousandtwentyfour while the Swedish would be twentyhundred twentyfour.
I used to be a programmer myself (originally studied it for game design but now I'm a 3d animator) and it's why there's a specific default data structure built in to most programming languages to handle dates and internationalization of those dates.
If you really need a specialized toolset to handle managing dates and times in a program beyond whats already there, then find a library that has the tools you're looking for or make it yourself if it doesn't exist. Extending the date class is always an option.
I'm talking about sotware they produce and my employer buys that i'm expected to use.
I can't rewrite their "tools" and databases and fucking awful cloud-web front end things.
I tend to think multi-billion$ shitware companies should do that; but even so no way I'd be allowed.
Yes, I do end up having to write my own tools choosing whatever free stuff I'm allowed to have, or can get working,
Yes, It's incredibly easy in any half way decent (including free) software, far from rocket science, that is until you try to put something back into a database via one of these "tools".
So you work around, pre-processing, post-processing, get it working. Then they unexpectedly release a "patch" that sees through my work-a-round and tries to convert the thing i'd convinced it to treat as string into a screwed up datetime again.
Next time, I will prepend "fuckoracleiquit" to all datetimes before they go into the database.