The Impermanence of Software
summary
Examines how software is intentionally or inevitably built to decay, using three case studies that trace failures in code, deployment, and data migration. Describes concrete tools and practices used: Ruby applications and migrations, container snapshots, simple SQL rollbacks, and reports finding thirty-two legacy scripts; also describes rebuilding a subsystem that is fully tested and retired rather than repeatedly patched.
AI-written summary · about
chapters (6)
- 0:00Welcome
- 1:44Digital system fragility
- 10:42Software impermanence examples
- 20:01Ephemeral software legacy
- 27:09Tech progress reflections
- 31:12Closing
related talks
54mKeynote: Growing Old
35mThe Dawn of Liquid Software
26mSoftware Delivery from First Principles
40mHow to fail a software project fast and efficiently?
29mLooking under the rug: the art of learning from failure
48mUnbreakable by Design: The Secret Tech of Antifragile Software
23mDevOps and Legacy Code
36mWe Have a Complex Systems Problem…and We Need to Talk About It