sethserver.com Subscribe
A cartoon robot character with a turquoise square body, large circular eyes, and red/purple striped arms is shown in a panicked state with an orange explosion effect above its head, motion lines at its feet, and blue sweat drops, all set against a pale yellow background.

It's Not about Crushing Success, It's about Recovering from Catastrophic Failure

By Seth Black • Updated: January 26, 2026

Startups · 2 min read

Like this kind of writing? Get one email a week with notes on startups, AI, and the occasional strong opinion about Python: subscribe to the newsletter.

My wife has worked as a chef since before we met. Something that I've learned to watch for in restaurants how well the staff handles a rush.

If you've ever worked in a restaurant, or even in the service industry you know that rushes happen all the time. We lived in Austin for over a decade, and I know that "oh gawd SxSW" look. It's a seasonal emotion.

What matters is what people do when things are already sideways and then the rush shows up anyway.

Another fun thing I've had the privilege of doing is watching her work for new restaurants through grand opening. It's like a startup but with no cash incentive. Seriously, restaurant people are nuts. Prep isn't done. The produce order hasn't been put away. One of the coolers is doing a fun new thing called "not being chill". And then the lunch rush hits.

The good people just start executing. They take care of the next thing in front of them and keep the line moving (if you've worked in a restaurant you'll see what I did there).

Then comes failure mode: the GM (or worse, the overly-hands-on owner) jumps on the line, or starts unpacking orders, takes over expo. They're trying to help, but they don't know the system well enough, so they create new problems faster than the team can solve the old ones. I literally watched this happen at a restaurant a few days ago (at the time of original writing...who knows how far into the future you're reading this - hopefully the future is better). So the feeling is fresh in my mind.

Tech people love the idea of "crushing it." But most real success isn't rocket ships and unicorn ninjas. It's how you handle the inevitable major failures, or daily medium inconveniences that happen.

Here's the tech version of the restaurant cooler dying mid-service:

Logging wasn't set up on prod.
Alerts are down.
Nobody backed up the database.
And now we have a production outage.
Wee.

The military is an extreme example of this, they'll literally train people to take orders and do their job when under hostile enemy fire. Literally you could die, but damnit get that radio working! Most of us are not under enemy fire. We are just under Slack fire, which feels similar but with less metal and fewer medals.

Here's the trick: If anything, know your position. Are you an operations person, well when things are going sideways make sure things keep moving. Leader? Get out front and talk to angry customers. Take the heat so the team can recover. Middle manager? Eek. I'm pretty sure you're going to be replaced with AI soon.

If you build systems - restaurants, startups, or anything in between - optimize for recovery. The rush is inevitable. The mistakes are guaranteed. The real skill is learning how to get back on your feet fast.

-Sethers

Share this post
Newsletter

One email, once a week.

Notes on databases, systems, and the occasional strong opinion about Python. No spam, unsubscribe anytime.

Seth Black
Written by

Seth Black

Engineer and founder based in Texas. Writes about databases, AI, and running things in production. Embeds in small teams as lead engineer.

More from Startups

View all →
Startups

What Actually Goes in a Consulting Contract

Sep 17, 2026
Startups

Productizing a Service: From Hours to Licenses

Jul 26, 2026
Startups

The MVP That Is Not a Product

Jul 11, 2026