*22/2/22
You know how the date looked strange to you? It’s the same for your correction, but for other people
For a statistically insignificant portion of people, sure. It doesn’t make it any less correct.
Slack’s Incident on 2-22-22
21–30 of 183 posts
Re: Slack’s Incident on 2-22-22
#22That date format is actually the worst I have ever encountered. m-d-y, with year in 2 digits, numbers not zero-padded, US "order" yet using dashes. It's like a moderator of /r/ISO8601 came up with the worst possible format on purpose . Am I missing something?
I mean, there is literally no way to confuse it with another date, unless you go back 100 years, when Slack didn't exist.
There is no 22nd month, so we know the 22s are the day and the year, leaving only the 2 to be the month. Is it really that difficult to parse?
Re: Slack’s Incident on 2-22-22
#23Earlier quoted context omitted.
You know how the date looked strange to you? It’s the same for your correction, but for other people
For a statistically insignificant portion of people, sure. It doesn’t make it any less correct.
For the whole of Europe it would be 22.02.2022, how is all of Europe statistically insignificant?
Re: Slack’s Incident on 2-22-22
#24That date format is actually the worst I have ever encountered. m-d-y, with year in 2 digits, numbers not zero-padded, US "order" yet using dashes. It's like a moderator of /r/ISO8601 came up with the worst possible format on purpose . Am I missing something?
I mean, there is literally no way to confuse it with another date, unless you go back 100 years, when Slack didn't exist. There is no 22nd month, so we know the 22s are the day and the year, leaving only the 2 to be the month. Is it really that difficult to parse?
I'm so tired of having to do that game every time I see a date. It is not hard, but it is quite annoying. Especially since it isn't solvable in a lot of cases, so you try to reason your way to the most realistic interpretation.
It shouldn't be this hard.
Re: Slack’s Incident on 2-22-22
#25That date format is actually the worst I have ever encountered. m-d-y, with year in 2 digits, numbers not zero-padded, US "order" yet using dashes. It's like a moderator of /r/ISO8601 came up with the worst possible format on purpose . Am I missing something?
I mean, there is literally no way to confuse it with another date, unless you go back 100 years, when Slack didn't exist. There is no 22nd month, so we know the 22s are the day and the year, leaving only the 2 to be the month. Is it really that difficult to parse?
I just thought it was a typo.
Re: Slack’s Incident on 2-22-22
#26Earlier quoted context omitted.
I mean, there is literally no way to confuse it with another date, unless you go back 100 years, when Slack didn't exist. There is no 22nd month, so we know the 22s are the day and the year, leaving only the 2 to be the month. Is it really that difficult to parse?
I'm so tired of having to do that game every time I see a date. It is not hard, but it is quite annoying. Especially since it isn't solvable in a lot of cases, so you try to reason your way to the most realistic interpretation. It shouldn't be this hard.
It’s not really that hard. Like the imperial system, Americans just memorize how it works as children and don’t think about it anymore.
Think about it like speaking a different language, except with numbers and not words.
Re: Slack’s Incident on 2-22-22
#27Earlier quoted context omitted.
I certainly wouldn't trust it's availability. (The original McDonald's McRib sandwich is well known for only being sold a limited time.) So "Mcrouter" comes from Memcache-Router, then the obvious McDonalds jokes are made and someone cleverly suggests "Mcrib" for the next service. But I can't think what the backronym would be for it. Memcache Ring Buffer maybe. Or Broker.
Apparently it generates configurations for Mcrouter. Could be MemCache-Router Instance Borker.
I think you meant Broker, but the misspelling is an act of genius since we are talking about downtime caused by an infrastructure failure.
Re: Slack’s Incident on 2-22-22
#28Earlier quoted context omitted.
For a statistically insignificant portion of people, sure. It doesn’t make it any less correct.
For the whole of Europe it would be 22.02.2022, how is all of Europe statistically insignificant?
The official EU rules say 22.02.2022, but nobody in Europe would have trouble parsing 22/2/22 or any variation thereof. And the / (or -) separator is indeed used in parts of the EU.
It’s the ordering that’s significant, not the separator.
Re: Slack’s Incident on 2-22-22
#29That date format is actually the worst I have ever encountered. m-d-y, with year in 2 digits, numbers not zero-padded, US "order" yet using dashes. It's like a moderator of /r/ISO8601 came up with the worst possible format on purpose . Am I missing something?
I mean, there is literally no way to confuse it with another date, unless you go back 100 years, when Slack didn't exist. There is no 22nd month, so we know the 22s are the day and the year, leaving only the 2 to be the month. Is it really that difficult to parse?
> leaving only the 2 to be the day
I think you meant "to be the month" there. qed■
Re: Slack’s Incident on 2-22-22
#30Earlier quoted context omitted.
I'm so tired of having to do that game every time I see a date. It is not hard, but it is quite annoying. Especially since it isn't solvable in a lot of cases, so you try to reason your way to the most realistic interpretation. It shouldn't be this hard.
It’s not really that hard. Like the imperial system, Americans just memorize how it works as children and don’t think about it anymore. Think about it like speaking a different language, except with numbers and not words.
The complaint isn't about the particular other order, but the fact that the order is ambiguous. In this case that doesn't matter, but often it does.
Americans memorize inches and yards, and often also memorize centimeters and meters, and working with either is fine, but we're not so often faced with numbers where it might be inches or centimeters and we have to figure out which (and when we are, it's sometimes a pain - certainly a bigger pain that working with known units).
Or, working with your language analogy, please go fetch me some "pasta" without knowing whether I'm speaking Italian or Polish.