That 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?
Slack’s Incident on 2-22-22
31–40 of 183 posts
Re: Slack’s Incident on 2-22-22
#32McRib is a hilarious name for a service
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.
Re: Slack’s Incident on 2-22-22
#33That 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?
It doesn't seem that bad to turn it into 2-22-22.
Re: Slack’s Incident on 2-22-22
#34Earlier quoted context omitted.
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…
Re: Slack’s Incident on 2-22-22
#35That 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
#36Earlier quoted context omitted.
Quoted post unavailable.
This sort of handwavy conspiracy thinking is distressingly common. What basis do you have for your suspicion? Is it just “big company bad”?
Re: Slack’s Incident on 2-22-22
#37Earlier quoted context omitted.
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…
Context matters in your pasta scenario.
Re: Slack’s Incident on 2-22-22
#38Re: Slack’s Incident on 2-22-22
#39Re: Slack’s Incident on 2-22-22
#40An over communication platform should have scheduled outages like this regularly!