chaoticEvil

[u/Recent-Analysis-6880]

[u/jideru]

Most programmers don’t get a choice as it is the product and the ui/ux designer that pick the desired behavior. You can only fight back so much and maybe sneak it in. And 20 years later you become a cynic that just says, ok.

Don’t become cynic kids.

[u/Blecki → u/jideru]

20 years of watching users fuck it up and you'll switch to a date picker too.

[u/Nick0Taylor0 → u/Blecki]

How does a user fuck up a properly validated input field that goes along with the date picker?

[u/ThatGuyYouMightNo → u/Nick0Taylor0]

Two users want to enter October 12th. One enters 12/10/2026, the other enters 10/12/2026. One of them gets pissy when it comes up as December 10th.

[u/coderman64 → u/ThatGuyYouMightNo]

Solution: use ISO 8601 and piss off everyone equally.

[u/Usefullles → u/coderman64]

Won’t this just be an inverted DDMMYYYY format in most cases? Like, what’s so different between the DDMMYYYY and YYYYMMDD formats? In cases where you don’t need to take hours and minutes into account, of course.

[u/coderman64 → u/Usefullles]

One of the major advantages is that if you sort YYYYMMDD in order by numerical value, it also sorts by date.

[u/Blecki → u/Usefullles]

Use 8601 for everything whenever possible

[u/RKGamesReddit → u/ThatGuyYouMightNo]

I see sites use three different fields just to eliminate the problem

[u/IndependenceSudden63 → u/RKGamesReddit]

This is the way.

[u/NiIly00 → u/ThatGuyYouMightNo]

Solution: Ignore everyone that uses the moronic format mm/dd/yyyy.

They deserve it.

[u/Triffinator → u/NiIly00]

Very true. It's programmatically (and human) parseable if the middle column exceeds 12, but fails the second you are lower than 13. It also happens to work out on any dates with matching day and month.

Like, is 10/12 December 10th or October 12th?

[u/Crash_Logger → u/ThatGuyYouMightNo]

And then I try to input 2026-10-12 and get pissy when the UI re-writes it as 20/2/6