The Social Coding Contract
summary
Argues that convenience creates a Jenga tower of dependencies and gives concrete failures: npm’s deep node_modules triggers Windows max path errors, a broken dependency forces a project to fork red_square to fix a postinstall script, and semantic-versioning mismatches silently break apps. Describes maintainer life: rapid early adoption, then maintainer burnout from trolls and unpaid patch work, recommends higher‑fidelity communication and borrowing systems‑level rigor (cargo/Go/Rust) and the “slow code” approach.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:53Open source is good
- 5:40Open Source Progress
- 12:24Early Adopters
- 16:09GitHub Threads
- 17:49Trolls
- 19:08Open Source
- 19:52Trust
- 20:23Marketing
- 21:05Ant
- 22:41Semantic Versioning
- 23:30transitive dependencies
- 24:09What is open source
- 24:55How to communicate online
- 25:42Troll repellent
- 26:49The future
- 27:29Innovation
- 28:59Understanding Debt
- 29:45Hosted vs Embedded Systems
- 30:43Systems Engineers
- 32:37Conclusion
- 33:58Contact Information
related talks
44mThe Social Coding Contract
16mDependency Hell Just Froze Over
27mDependency hell - Or, Developers' perception of software dependencies
35mKnowing Your TCO (Total Cost of Ownership)
42mSponsored Session: Dependencies: Do's and Don'ts
27mThe code etymologist
35mBroken Promises in Open Source
57mZen and the Art of Package Management