The Social Coding Contract
summary
Social coding produces deep, fragile dependency graphs: an empty Rails app has 50 gems -> 75–100 after real use, npm creates trees that hit the npm path limit, and version resolution conflicts leave 272 gems failed to install in one example. A production app breaks when a transitive dependency publishes a breaking change and lineman must fork and maintain it. Proposals include a dead-man's-switch app for repo handoff, decentralized package hosting, and coordinated corporate audits to fund security reviews.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:19THE SOCIAL CODING CONTRACT
- 3:25IN THE BEGINNING
- 3:46INDUSTRIALIZATION
- 14:04MAINTAINER EARLY ADOPTER
- 15:04MAINTAINER EARIY ADOPTER
- 19:51ASYMMETRIC POWER
- 34:53SIMMERING DISDAIN?
- 39:23high level
- 40:24DEPTH OF UNDERSTANDING
related talks
35mThe Social Coding Contract
35mMaking it on your own and the pitfalls of gem dependencies
40mDependency Management: The Cause of—and Solution to—All Supply...
42mSecuring Your Software Supply Chain
05mDependency Demons
30mDependency management: the cause of—and solution to—all supply chain problems
42mSponsored Session: Dependencies: Do's and Don'ts
27mDependency hell - Or, Developers' perception of software dependencies