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.
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.
I highlight how mapping software execution to music can help developers spot bugs. I believe sonification techniques are broadly applicable to complex datasets like DNA sequences and time series, turning abstract data into audible patterns.
I increasingly use coding agents to build one-off tools and run reusable software, from UMAP visualizations to receipt classification. I think agents will become both software's users and its universal wrapper, reshaping familiar developer roles.
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.