Technical Enshittification: Why Everything is Horrible and How to Fix It
summary
Companies ship broken products because of rigid deadlines, huge technical debt, and bad org decisions, not because features are hard. Examples: Sonos new app hits 200,000 reviews and 1.2 rating after a May 7 release, legacy code bases span 20 years, developers code under one hour/day and lose 25 minutes after each distraction. Security and scale harm quality: CrowdStrike outage causes global airline groundings, 50 million LOC to open a garage door, 700,000 malicious packages in supply chains, and 40% of AI‑generated code contains vulnerabilities.
AI-written summary · about
chapters (10)
- 0:00Introduction to enshittification
- 1:06What is ancientification?
- 3:41About the speaker and context
- 6:09Examples of software failures
- 13:05Bloat and security vulnerabilities
- 20:13Stagnation and lack of innovation
- 29:52Why Sonos app failed
- 34:37Productivity killers in software
- 40:12How to fix software development
- 50:51Helping the business and conclusion
related talks
48mTechnical Enshittification: Why Everything in IT is Horrible Right Now and How to Fix It
28mTechnical Debt: Why it'll ruin your software
13mTen Ways to Doom Your DevSecOps
52mUnderstanding UnHealthy Syndromes of Software Delivery
37mKeynote - You are Load Bearing
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
36mWhy programming is fiendishly difficult and what we can do about it
27mThe human cost of development