Crash-Only Thinking
A few weeks ago, I learned about something called crash-only software (ht, Robert Greco). This is software that has no normal “start” or “stop” mechanisms. It can only be s…
Highlights Tour This post is part of the highlights tour, a series of historically significant ribbonfarm posts A few weeks ago, I learned about something called crash-only software (ht, Robert Greco ). This is software that has no normal "start" or "stop" mechanisms. It can only be stopped by crashing it. Often this means unplugging the computer physically. It can only be restarted through some sort of failure-recovery routine, with a hard reboot being the most extreme kind. There's a whole theory of crash-only software design apparently. Discuss with vgr_zirp → The idea of crash-only design
Explore this link on the map →related reading
- John Carmack on Idea Generationamasad.me
- Mental Models: The Best Way to Make Intelligent Decisions (~100 Models Explained)fs.blog
- On rebooting: the unreasonable effectiveness of turning computers off and on again - Keunwoo Lee's Minimum Viable Homepagekeunwoo.com
- Stables and Volatiles – Rands in Reposerandsinrepose.com
- BlitzFail: How Not to Go Off the Rails | by David Sacks | Craft Ventures | Mediummedium.com
- Welcome, friend - Inverted Passioninvertedpassion.com
- Hiring (and managing) cracked engineers - PostHogposthog.com
- Adapting_to_Endure_May_2022.pdfcontent.fortune.com
- Malcolm Ocean • culture, change, and mental modelsmalcolmocean.com
- BlitzFail - Bottom Up by David Sackssacks.substack.com
- How Not to Diepaulgraham.com
- What the Stockdale Paradox Tells Us About Crisis Leadership | Working Knowledgehbswk.hbs.edu