I shared a collection of famous software glitches, ranging from Patriot missile failures to the wobbling Millennium Bridge. These resources document high-stakes computer errors and provide historical context for system verification and software quality.
Speaking of bugs, here are some famous software glitches – right from the Patriot missiles misfiring to the London Millenium bridge wobbling. Some links are broken, though. (More glitches and links)
I've linked a collection of software horror stories that demonstrate how critical bugs can lead to real-world fatalities. These cases underscore the life-and-death stakes and the necessity of rigorous safety-critical software engineering.
Review essential truths and myths of software development, including the 28x productivity gap, the high cost of maintenance, and why software estimation often fails due to poor timing and incorrect stakeholders.
Software is shifting from fixed reusable tools toward agent-driven execution, where coding agents increasingly become the interface through which software is created and operated.
I explore the concept of apologetic software, which uses human-like social scripts to apologize for system errors. Research suggests that software taking responsibility for its mistakes significantly reduces user frustration and improves the overall interaction experience.
I recommend Joel Spolsky's writing on software development, specifically his insight that good software takes ten years. It is a foundational read for understanding the long-term dedication and refinement required to build successful products.