The Open Source Effect
summary
Describes building a tiny PHP client for existdb that ends up with four downloads, then the first Java patch produced after two days of setup; contrasts maintaining an original project versus contributing to established ones; shows one-line fix saved 6,000 lines of company workaround by adding one line and six test lines; logs ~1000 bug reports to Eclipse as career fuel; cites a JUnit dependency upgrade that leads to funded work, and points out practical tools like pressing dot on GitHub to open VS Code.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:20Who am I
- 2:59Why open source
- 3:52Open source adventure
- 4:53My first open source project
- 10:00First contribution to a large open source project
- 13:37First code contribution to a large project
- 19:45Contributing to open source can also mean
- 23:55Gaining expert knowledge
- 26:00Obvious things
- 27:13Ask the maintainers
- 29:50Hack and hack
- 31:45Get your hands dirty
- 37:52Sponsorship
- 39:35Outro
related talks
33mThe Open Source Effect
43mUsing Open Source for Fun and Profit
29mThe Open Source Development Surprise
26mHow open-source made me a better developer
41mUsing Open Source for Fun and Profit
32mExemplars, Laggards, and Hoarders: A Data-driven Look at Open Source Software Supply Chains
46mThe Unexpected Demise of Open Source Libraries
34mHow Open Source Helped My Career: A History from an Average Joe
