How to Reverse Software Entropy
summary
Entropy increases because real systems accumulate hidden complexity: a brand new create‑react‑app pulls in 3114 transitive packages, a single 11‑line left‑pad module once broke thousands of builds, and a January government shutdown takes the NIST CVE feed offline and breaks our build. Prescriptions are concrete: produce an SBOM, pin to SHA and serve deps from an internal registry, use executable fitness functions to enforce architecture, prefer unit tests over brittle UI tests, and follow red-green-refactor TDD to keep cognitive load and over‑engineering down.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:43Software and Physics
- 3:08Second Law of Thermodynamics
- 4:34What is Entropy
- 9:15Qualitative Measures of Entropy
- 10:03Dependency Forest
- 11:16Create React App
- 11:48Test
- 13:54LeftPad
- 15:07Creating a Software Bill of Materials
- 18:54The Test Pyramid
- 19:47UI Driven Testing
- 24:04Progressive Test Anemia
- 24:46Test Anemia
- 27:11Broken Build
- 28:02Test Driven Development
- 28:20No Magic Sauce
- 29:56Engineering
- 31:06Mercedes eccentric wiper
- 33:33Cognitive Load
- 34:55Agile Manifesto
- 35:49Baseball Analogy
- 37:39Federal Government Shutdown
- 39:44What do you do
- 41:28Defend against the horse
- 41:52Conclusion
related talks
25mIT & The Second Law of Thermodynamics
43mQuit Simplifying!
48mTechnical Enshittification: Why Everything in IT is Horrible Right Now and How to Fix It
52mEmbracing Complexity Entropy in Software Design
53mTechnical Enshittification: Why Everything is Horrible and How to Fix It
01h 01mGuide to Destroying Codebases the Demise of Clever Code
26mSoftware Delivery from First Principles
56mKicking the Complexity Habit