The downside is that to get more of a Facebook community experience with a calendar, files, and subgroups, you will probably have to pay for for the Premium level. https://groups.io/static/pricing

It includes PDFs of some relevant support pages that someone printed with their browser 5 hours ago. That's probably the right thing to do in such a situation to get this kind of info publicly available ASAP, but still, oof. Looks like lots of people in the Reddit thread had trouble accessing the support info behind the login screen.

What's crazy is that Snowflake made MFA enforcement available only 5 days ago.

For example https://erikdemaine.org/fonts/tetris/?text=%7D6G6C+8%40%3F%3...

Some companies require that. Here is PayPal's process for example: https://www.paypal.com/us/legalhub/useragreement-full#table-...

https://www.reddit.com/r/hacking/comments/16yrggi/aorg/

When we signed onto Snowflake in 2019, a week later a surprise HUGE box of swag arrived, with a dozen shirts and lots of other things. Our team and corner of the office became The Place To Be for a while.

― Kurt Vonnegut, Mother Night

Don't extrapolate too much based on a single quarter metric (albeit an important one). That's the HN way.

Here's one good excerpt:

Dickerson quickly established the rules, which he posted on a wall just outside the control center.

Rule 1: “The war room and the meetings are for solving problems. There are plenty of other venues where people devote their creative energies to shifting blame.”

Rule 2: “The ones who should be doing the talking are the people who know the most about an issue, not the ones with the highest rank. If anyone finds themselves sitting passively while managers and executives talk over them with less accurate information, we have gone off the rails, and I would like to know about it.” (Explained Dickerson later: “If you can get the managers out of the way, the engineers will want to solve things.”)

Rule 3: “We need to stay focused on the most urgent issues, like things that will hurt us in the next 24–48 hours.”

A colleague told him about the Two Trains Problem (https://mathworld.wolfram.com/TwoTrainsPuzzle.html), and Von Neumann replied with the correct answer. When his colleague said, "Ah! You figured out he trick!", Von Neumann replied, "What trick? I just summed up the distances in my head!"

Then in the post-mortem about lack of backups:

> LVM snapshots are by default only taken once every 24 hours. YP happened to run one manually about 6 hours prior to the outage > Regular backups seem to also only be taken once per 24 hours, though YP has not yet been able to figure out where they are stored. According to JN these don’t appear to be working, producing files only a few bytes in size.

I have had (and inevitability will have again) bad days like poor YP. All I can count on is to maintain good habits, like making backups before undergoing production work like YP did.

It's also useful to have the Unified Remote server [2] running on the media computer so you can control it from your phone when you need to.

[1] https://www.newegg.com/p/09N-00A7-00001

[2] https://www.unifiedremote.com/

Perhaps Databricks suspected another big announcement coming soon and wanted to get this announcement out?