How to Become a Top-Performing Software Engineer through Open Source..
summary
Claims that open source practices make engineers more promotable and let companies adopt InnerSource with measurable wins including 500 InnerSource use cases and industry scale (JVM 25+ years, IBM bought Red Hat for $34B, 97% of apps use OSS). Concrete practices: require docs + tests in PRs, use ADR and C4 model for architectural decisions, add mutation testing to reveal that roughly half of flimsy tests need refactoring, run integration suites with testcontainers and JUnit Jupiter, and measure results by change logs, API docs (OpenAPI), and reduced onboarding time.
AI-written summary · about
chapters (13)
- 0:00Introduction to open source
- 1:13Open source as industry power
- 3:40Software engineering with people
- 5:48Code review and CI/CD culture
- 7:14Open source engineer credibility
- 8:19Define the reason first
- 9:23Documentation and tests importance
- 12:32Software documentation best practices
- 13:58Testing strategies and integration
- 14:39Communication skills for engineers
- 15:44Staff engineers and leadership
- 16:27Code simplicity and design patterns
- 17:09Summary and key takeaways
related talks
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
54mInnerSource 101 and the Apache Way
31mLeveraging your Organization's OS Engagements to Recruit and Retain.
47mHow Should Your OSPO Work with InnerSource?
47mWhat Is InnerSource? How Do You Implement It ...
15mAdopting Open Source Practices To Build More Inclusive Products and Services
26mWhy innersource is a critical component of FOSS sustainability
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change