Issue: there are 27 different ways of writing a date.
Engineers: We most make a common standard that is unambiguous, easy to understand and can replace all of these.
Issue: there are 28 different ways of writing a date.
Joke aside, I really think the iso standard for dates is the superior one!
2013-02-27 = 1984
@m_f@discuss.online this might be applicable to the farside as well
Do you mean the post titles? I’ve been using the same format as was used since before I took over posting, but if people want ISO format that works for me
I’m all for ISO format. I can’t imagine anyone having objections.
I agree with the ISO approach, but unfortunately without mainstream adoption in a majority of countries it’s just another standard.
In the last company I work for, the department was created from zero, and my boss just let me take all the technical decisions so from the begging everything was wrote in ISO-8601. When I left it was just the way it was, if you try to use any other date format anywhere something is going to give you an error.
I was going to comain until I realized that the fprmat is the one that I prefer.
This is the way.
2013-02-27 is a weird way of writing 1361923200
I just don’t like to be forced to include the damn year everytime, and if you cut the year from ISO 8601 you get the american MM-DD order, which everybody hates.
I like DD/MM/YYYY. 🤷🏻♂️
If it’s just in casual conversation or emails DD/MM/YYYY is fine, but if you’re naming documents or something in a professional setting, you should really always include the year anyway.
Everyone should use date-time groups so we’re all on the same page down to the second.
DDHHMMSSZmmmYY
%Y%m%dT%H%M%SZ
Working for a global clinical research company, DD-Mmm-YYYY is the easiest for everyone to understand and be on the same page. It’s bad enough identifying which date you’re capturing in metadata without also trying to juggle multiple date formats.
As a Hungarian, I approve.
As an American, I can’t get people in my team to standardize their email signatures with correct spelling.
Sounds like something a terrorist would say.
The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…
The BEST way is to use the number of seconds after the J2000 epoch (The Gregorian date January 1, 2000, at 12:00 Terrestrial Time)
Generally yes, that’s the way to do it, but there are plenty of times where you need to recreate the time zone something was created for, which means additionally storing the time zone information.
Definitely. If your servers aren’t using UTC, then when you’re trying to sync data between different timezones, you’re making it harder for yourself.
This is what I try to do in the few apps I’ve written that had to deal with dates and times
deleted by creator
I think you skipped part of the sentence.
I’m not a computer and this isn’t work so I’m gonna just use my confusing date format.
