Crowdsourcing platform engineering
summary
Crowdsourced platform engineering builds shared ownership through visible weekly updates, a prioritized backlog and short scoped issues, public recognition, empathy interviews, and short role rotations. Concrete wins: implemented release tagging, migrated from Firebase test lab to an in-house Android test farm, CI times drop from >40 to <19 minutes, roughly 4,000 developer hours saved per year, 60 engineers attend a developer productivity day and one contributor wins promotion — all demonstrating the system works.
AI-written summary · about
chapters (11)
- 0:00Crowdsourcing platform engineering
- 4:02Centralized platform problems
- 8:00How crowdsourcing works
- 10:27Five-component shared ownership
- 11:09Making platform work visible
- 12:50Enabling platform contributions
- 14:39Public recognition for contributions
- 16:46Building team empathy
- 18:54Role rotation for understanding
- 20:39Results and impact
- 22:05Key takeaways
related talks
29mSuccessful Cloud Native Platform Engineering – Hype vs Reality
15mEstablishing Platform Teams to Utilize the Economy of Scale
29mImproving Developer Experience
28mBoosting your Engineering Culture & Community through Gamification
18mPlatform Engineering Meets SCM
49mBuilding an engineering platform
47mDesigning the Developer Experience
46mCrowdsourced learning and Software Development as part of a Distributed Team