How Open Source Development Can Make You A Better Developer
summary
Five years of OSS work, 6000 GitHub stars, and a contribution landed in Swift lead to concrete lessons: building a pull-to-refresh control, a Harvey update alert library, and floating‑label text controls; adopting CocoaPods, Carthage, Swift Package Manager, and Travis CI for releases; learning string transliteration and platform availability APIs; handling localization, issue templates, and maintainer cadence; and gaining confidence from real integration and adoption numbers rather than vague promises or examples.
AI-written summary · about
chapters (22)
- 0:00Intro
- 4:274 Types of Open-Source Projects Based on Adoption?
- 7:27Journey into the past, to a time before
- 10:39Drive+by Porsche & Ducati Community for Ducati
- 15:17The Float Label Pattern 8 9 10
- 17:10Swizzling UITextField's Clear Button
- 19:46Experimenting with APIs You Normally Wouldn't Use 11
- 25:05Harpy & Siren
- 27:37Package Managers
- 31:13Continuous Integration
- 32:26Internationalization (i18n) & Localization (110n)
- 34:16Being a Maintainer vs. Being a Consumer
- 35:53Contributing to Swift
- 37:06Contributing to Established Projects (1/2)
- 38:31Creating Your Own Project
- 39:59Marketing your Library
- 40:53Issue Templates
- 41:30Pull Requests vs. Issues Turn off issues in favor of pull requests 13
- 42:25Network of Trust
- 43:19Deprecating A Project
- 43:42Passing the Torch
- 44:00From The Shark Tank
related talks
34mOpen Source is Awesome: How it Makes us all Better Developers
26mHow open-source made me a better developer
24mOpen Source & Swift
51mMy awesome journey with Open Source
29mThe Open Source Development Surprise
33mThe Open Source Effect
27mDesign Your Open Source Project
34mHow Open Source Helped My Career: A History from an Average Joe