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
11–20 of 183 posts
Re: Slack’s Incident on 2-22-22
#12Sometimes new roll-out causes outage, sometimes, roll-out are delayed due to the overall system architecture. Reading the post-mortem, I could not help but be reminded of this issue as described here: https://www.youtube.com/watch?v=y8OnoxKotPQ
Re: Slack’s Incident on 2-22-22
#13McRib 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.
memcache router interface broker
Re: Slack’s Incident on 2-22-22
#14McRib 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.
Apparently it generates configurations for Mcrouter. Could be MemCache-Router Instance Borker.
Re: Slack’s Incident on 2-22-22
#15> including the author — which certainly made my role as Incident Commander more challenging!
As if no other way to communicate exists?
I remember using Slack, feeling fed up with emails, until I realized that if I wanted to sync Slack messages offline and have a standard way to view these messages that I was SOL. I am so glad that I've returned to email and optimized my workflow to use email effectively and efficiently. The best part is no more vendor lock-in.
Re: Slack’s Incident on 2-22-22
#16*22/2/22
Re: Slack’s Incident on 2-22-22
#17A Date that is both a Palindrome and an Ambigram: https://www.jagranjosh.com/general-knowledge/22-02-2022-is-b...
Well, not the way they format it.
Re: Slack’s Incident on 2-22-22
#18That 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's a quirky nod to the fact that all the digits were 2 on that day in this format.
Re: Slack’s Incident on 2-22-22
#19That 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?
This is what you sometimes see for best-before dates in Canada. Even better, because our dates are “supposed to” be like 22/2 but I don’t think anyone here does that, except Quebec perhaps. Sometimes you just have no clue
Re: Slack’s Incident on 2-22-22
#20*22/2/22
You know how the date looked strange to you? It’s the same for your correction, but for other people