Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise.

Except for, yknow, human readability

But dd-mm-yyyy is better for day to day daily life usage

Uh, no.

And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a named fork Alternate Data Stream.

This is the (year-month-) day.

The last star of the Greek alphabet? 🤷🏻

A Warrior Cats and Omegaverse crossover character

I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone.

If you work at a company where all of its offices are in the same time zone and you're time-stamping logs, then it's more expedient for understanding and placing an event in time against other things to use local time.

Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.

"I got your email at 20:37:45-7:00" is a few more steps than "I got your email at 1:37PM".

It's not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.

Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more "workable" compromise.