Anyone who has worked the IT desk knows how users are. Reading is against their beliefs.
The possibility of servicing users that are american scares me…
Been working IT at a public school for almost a year, have never once got an answer to the question "and what did the error message say?"
Got a ticket yesterday with the text "I can't install addins in office anymore. I only get this message"
Then they attached an image of office telling them exactly why they can't install addins (optional experiences is disabled) and exactly where to go in the settings to enable it again...
A friend asked for some computer help and when I asked him to replicate the problem, he closed the error window before I could read it. I think that was when I gave up helping people with their computer problems.
yyyy-mm-dd supremacy
ISO 8601 FTW
Rather go with RFC 3339, a standard that is openly available for anyone to read.
I was going to write something sassy, but separating the date and time portion with a T is marginally superior. I love them both!
Hey man, try reading the words on the screen above the inputs.
You ever tried to do that AND be a redditor at the same time?
Tsk... these elitist lemmings... smh.
While this problem is dumb, you could eliminate the class of user errors by having months be selected by name
Done…

Oh no
New month names just dropped:
- Joctober
- Novemy
- Deculyary
- Febrarch
- Munepril
- Septanugust
Perfection
Ah yes the month of febroctougust
Technically, we can eliminate this class of user errors by holding up YYYY-MM-DD as the one true method of dating and smite the nonbelievers.
We're generally not allowed to smite the end users at work, satisfying as that may have been.
We can mostly just hope to keep that standard within the codebase, and seek alternative means of eliminating error classes for end users
clearly its the month of SMARCH. or smapril.
People born in the first 12 days of any given month live happier.
But gets the date all wrong. Except for a subset of them...
Don't worry, be happy.
Facepalm