This is why we can't have nice things!
summary
Argues that small, local tech choices create global pain: ancient protocols and design tradeoffs force brittle workarounds. Cites SMTP retries take up to five days as a concrete surprise, points to HTTP/SMS and dependency chains that bloat features, and shows engineers either forking libraries or patching registries where mutable registry tags let images be silently rewritten. Describes using container registries, tag immutability, and library forks as actual fixes, notes the cost is ongoing maintenance and complexity, and recommends pragmatic, backward‑compatible changes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:51Simple protocol problems
- 5:26Legacy protocol complexity
- 8:17Internet design origins
- 10:27Software evolution
- 13:01Coding style differences
- 16:17External library reliance
- 18:25Code transparency importance
- 20:14Development pragmatism
- 21:47Guidelines role
- 23:40Versioning challenges
- 25:07Closing remarks
related talks
29mThe Social Coding Contract
26mCommunication: What are you Thinking About?
32mLife As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors...
43mGood or bad - a key skill for developers
39mDevelopers kryptonite
50mFallacies of Software Development
50mConscious Coupling for Anti-fragile Engineers
59mThe Tech Lead Elevator: Real Stories and Hard Lessons