What this outage teaches you is that when a third party vendor fails and the internet breaks you can point the finger at them with no issues.

If your shit breaks and everyone else's shit is still working that's a problem.

> you can point the finger at them with no issues.

yeah sure, if your business is one of the 500 startups on HN creating inane shit like a notes app or a calendar, but outages can affect genuine companies that people rely on

I've been involved in public outages (i.e. major newspapers wrote articles about it) on one more than one occasion due to an outage, one was nearly 5 minutes long, the other only 20 seconds, both were terrible.

I learned that with crowdstrike. It completely changed my understanding of what's important for C-Suite and C-Suite wannabes that want to be in middle management

I tend to sell to a wide variety of customers. They tend not to give a crap if a cloud provider is down, its still our problem to make it right.

any company offering services with SLA that does not have this as a caveat is just crazy to me. "we guarantee our services will be up and running as long as the 3rd party services we run on top of are running."

Why do we need a plan for pennies?

Reporters et al always want 'a plan,' which is ironic because they have problems planning more than a week in advance.

Communication/language depends on shared context. The more context you share the shorter the trigger for evoking that thing and that context. And if you share no context communication becomes very difficult.

I wasn't aware that that idea was in dispute.

And honestly, without a lot more communication even with a person that speaks your language you have no idea if you actually have a shared context. While an American from NYC and one from some backwater town in Kansas share a lot of context but there is a lot of context they don't, so as communication becomes more detailed between them it's very likely that 'translation' between each other will be somewhat incorrect.

This is also why lawyer speak is so particular. Language is fuzzy in most cases. Only language that relates to discrete physical objects gets closer to the binary state of exactness described in the article.

Not retiring the debt was a choice.

The practical reason for not retiring the debt was that the world needs a zero risk benchmark.

The did retire the long bond, though.

Go Limp Go!

For all the engineers that say management doesn't matter, I give you David Limp.

Management doesn't matter until it does.

What makes you believe it was his management specifically instead of other factors? AFAICT he has been at Blue Origin for only a few years, so the root of their success may have been laid much earlier and they succeeded either because or despite his influence.

Not saying he's a bad manager, just that the fact this one launch was a success is not proof of his skills. Luck is definitely still a possibility. And as a sibling comment mentions, it's not like he has a flawless track record.

He was brought in to fix Blue's culture and try to speed things up, since the former Honeywell guy was taking forever to do anything.

I think it can be safely argued that since the fixes between attempt 1 and 2 happened entirely under him and faster than we're used to seeing from BO, he may have played a role.

It's more like Bob Smith was extraordinarily bad and David Limp is a reversion to the mean.

I worked under Dave Limp for multiple years in Amazon's Consumer Devices group (like way under, I think he was my manager's skip manager?). I like him personally. But:

(1) His management in the Consumer Devices group did not lead to success, I feel we (and especially the consumer robotics group) basically floundered for 7 years :(

(2) He only left Devices to join Blue Origin like 2 years ago. 2 years is a decent length of time, but far too short for us to credit this success to him -- there have been many other forces building Blue Origin to what it is today. Maybe he gets 30% credit?

p.s. no offense to Mr. Limp, I must emphasize that he was a kind, polite, caring person, and certainly had the capacity for great decisions. It is unfortunate that Consumer Devices and CoRo hasn't had great success, and success may yet be just around the corner.

And the people rejoiced!

The US is already the world's largest oil producer and has been for a while. We don't need venezuela's oil.

Time to update your cliches.

Isn’t this why we got involved in Iran in the 1950s?

It seems like a common thread for de-clouders is they run RoR.

"It works, until it doesn't."

The question is, at what point does it not work?

Vacuuming is grief enough. Rebuilding the index sounds like more of a nightmare than with Solr/Lucene. And what happens when indexing fails? In Solr/Lucene it used to mean you were dead. I'm sure they fixed that, but at some level you need to either be behind on one while you reindex or figure out some queueing system that works like transactions.

There are times when low power is better, because it allows the router to ignore far away clients.

In simple terms, far away = more work to communicate = more airtime = less throughput.

It probably only matters with multiple devices.