A Community of People, Not Projects
summary
A conference organizer recounts building CascadiaJS (200 people) then burning out and learning the concrete fixes: watch for family or work suffering, stop being the only person who can run an event, and make handoffs explicit. The surprising metrics are the number of dropped projects and revived events once leadership is shared. Practical tools include document in GitHub and IRC for asynchronous work and the cultural shift to prioritize people over projects so others can execute and scale.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:47SUPPORT YOUR LOCAL DEVELOPER COMMUNITY
- 14:38A FEW THINGS LEARNED
- 15:41WATCH FOR SIGNS THAT YOU'RE DOING TOO MUCH
- 22:342. FIND PEOPLE WHO SHARE YOUR PASSION
related talks
29m"Scaling a Rust Community: Lessons from the Frontlines"
48mThe community power in the developers life
46mCommunity BOF
32mRebecca Murphey - SeattleJS Conference 2017
47mTen Years of Community Organizer
18mHow to Keep Your Data Science Meetup Sustainable
33mBridging Connections
29mHow To Run A Successful Local User Group