Five ways open source will slow you down
summary
Claim: five concrete failure modes that make open source slow projects down and how to fix them. Examples: emailing maintainers demanding fixes (a team emailed a private address about 3,363 vulnerable artifacts after Log4Shell CVE-2021-44228), copy‑pasting libraries instead of using Maven/Gradle/Ivy/npm (loses upstream fixes), not filing issues with a minimal reproduction, and treating a quick tutorial as production understanding. Remedies: use dependency management, Dependabot/Renovate automation, report reproducible issues, and periodically review integrations.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 3:58What is software?
- 10:57Open source defined
- 21:34Consultant’s cautionary tale
- 27:40Five ways open source slows you down
- 33:05Turning open source into an accelerator
- 43:20Summary and conclusion
related talks
34mThe 10 Biggest Mistakes You Shouldn’t Make In Open Source
29mThe Unexpected Demise of Open Source Libraries
14mWhat can we do to make Open Source more sustainable?
37mIt’s Not Open Source, It’s You. Where Open Source Risk Comes From
10mThe Hidden Cost of Open Source
27mThrough the Looking Glass: How Open Source Projects See Vulnerability Disclosure
39mTalking with Management About Open Source
28mTalking with management about open source