Why the CrowdStrike bug hit banks hard
bitsaboutmoney.com · 3,289 words · saved by 1 readers
Regulation-induced monocultures meet unfortunate but explicable engineering decisions.
Why the CrowdStrike bug hit banks hard Patrick McKenzie (patio11) • Jul 31st, 2024 Programming note : I recently launched a weekly podcast, Complex Systems with Patrick McKenzie. About 50% of the conversations cover Bits about Money's beat. The remainder will be on other interesting intersections of technology, incentives, culture, and organizational design. The first three episodes covered teaching trading , Byrne Hobart on the epistemology of financial firms , and the tech industry vs. tech reporting divide . Subscribe to it anywhere you listen to podcasts. If you enjoy it, writing a re
related reading
- The banking crisis, two years latercomplexsystemspodcast.com
- Banking in very uncertain timesbitsaboutmoney.com
- THE 2028 GLOBAL INTELLIGENCE CRISIScitriniresearch.com
- How Crowdstrike failsfranklyspeaking.substack.com
- Debanking (and Debunking?)bitsaboutmoney.com
- Computers can be understood - Made of Bugsblog.nelhage.com
- KYC and AML: beyond the acronymsbitsaboutmoney.com
- Seeing like a Bankbitsaboutmoney.com
- More Than DNS: The 14 hour AWS us-east-1 outage – Jonathon Belotti [thundergolfer]thundergolfer.com
- 🧠 Banks are not disrupted.fintechbrainfood.com
- Vulnerability Research Is Cooked - Quarrelsomesockpuppet.org
- Notes on a non-profit indicted for bank fraudbitsaboutmoney.com