This chapter focuses on a state of emergency in Portland caused by a significant outage related to CrowdStrike, exploring accountability, public curiosity, and various theories about the cause. It examines the intricacies of operating systems, particularly the challenges of kernel mode and software dependencies, likening the digital ecosystem to a fragile house of cards. The discussion also highlights lessons learned from past mistakes in software development, emphasizing the importance of diversity in systems to prevent widespread vulnerabilities.
Robert Ross joins us in CrowdStrike’s wake to dissect the largest outage in the history of information technology… and what it means for the future of the (software) world.
Leave us a comment
Changelog++ members get a bonus 9 minutes at the end of this episode and zero ads. Join today!
Sponsors:
- Cronitor – Cronitor helps you understand your cron jobs. Capture the status, metrics, and output from every cron job and background process. Name and organize each job, and ensure the right people are alerted when something goes wrong.
- Retool – The low-code platform for developers to build internal tools — Some of the best teams out there trust Retool…Brex, Coinbase, Plaid, Doordash, LegalGenius, Amazon, Allbirds, Peloton, and so many more – the developers at these teams trust Retool as the platform to build their internal tools. Try it free at retool.com/changelog
- Socket – Secure your supply chain and ship with confidence. Install the GitHub app, book a demo or learn more
- Intel Innovation 2024 – Registration is now open for Intel Innovation 2024 in San Jose, CA!
Featuring:
- Robert Ross – Twitter, GitHub, LinkedIn, Website
- Jerod Santo – Mastodon, Twitter, GitHub, LinkedIn
- Adam Stacoviak – Mastodon, Twitter, GitHub, LinkedIn, Website
Show Notes:
Something missing or broken? PRs welcome!