I’m in the US. 90% of devs I work with write it in ISO 8601 anyways, even in emails or chats. Not only does it make sense, it also sorts logically and is more searchable (eg 2024-11-*).
We have :non-iso-8601: as a slack emoji to add when people use caveman date formats.
Granted we’re an international company across Europe and Americas, and have certainly run into confusion with messages like “the license expires on 4/7/25”
2 makes the most sense, and its also the international standard for dates in ISO 8601 / RFC 3339
I’m in the US. 90% of devs I work with write it in ISO 8601 anyways, even in emails or chats. Not only does it make sense, it also sorts logically and is more searchable (eg 2024-11-*).
We have
:non-iso-8601:as a slack emoji to add when people use caveman date formats.Granted we’re an international company across Europe and Americas, and have certainly run into confusion with messages like “the license expires on 4/7/25”
yup, and also good for sorting
I identify as an RFC 3339.