Podcast – Cory Doctorow's craphound.com Code is a liability (not an asset)
31 snips
Jan 19, 2026 The discussion reveals why code is seen as a liability rather than an asset. Maintainers face the misconception that code doesn't require ongoing maintenance. As technology evolves, software ages and breaks, leading to continual fixes. The podcast critiques AI's role in coding, emphasizing its inability to replace nuanced software engineering. Legacy systems are also highlighted, showing how technical debt leads to vulnerabilities. Ultimately, there's a warning about the future workforce needed to tackle the 'digital asbestos' of AI-generated code.
AI Snips
Chapters
Books
Transcript
Episode notes
Code Is A Liability Not An Asset
- Code's capabilities are assets, but code itself is a liability that accrues costs over time.
- The goal is code whose capabilities generate more revenue than maintenance and operational costs.
Software Engineering Versus Coding
- Writing code is distinct from software engineering, which focuses on long-term operation and failure modes.
- Software engineering designs for legibility, adaptability, and graceful failure across changing contexts.
Location Defaults Caused Real Harm
- Location-services defaults caused dangerous misreports, like placing unknown IPs at the center of the continental USA.
- These defaults once sent armed strangers to innocents and caused hours of distress for Doctorow's family.
