I'm fine with 2 systems, DD/MM/YYYY for general use because that's a good format for personal scheduling, but YYYY/MM/DD hh:mm:ss for anything involving work or industry because having the year first is useful for maintaining historical data.
Starting with the biggest bucket and searching down from there can save a lot of compute and search time.
Nah, it falls apart if you include time. YYYYMMDD hh:mm:ss makes more sense than DD/MM/YYYY hh:mm:ss.
how often do you write dates including the time? unless you're a programmer ddmmyyyy is obviously the easiest to use
Death to America
I'm fine with 2 systems, DD/MM/YYYY for general use because that's a good format for personal scheduling, but YYYY/MM/DD hh:mm:ss for anything involving work or industry because having the year first is useful for maintaining historical data.
Starting with the biggest bucket and searching down from there can save a lot of compute and search time.