The Hierarchy of Developer Needs
summary
Framework maps a Maslow-style Hierarchy of Developer Needs to concrete work: fix basic enablement first (clear docs, one-click app creation, target first-app in five minutes), then provide safe-harbor community (Slack/forums and external Stack Overflow), education (webinars, white papers, certifications) and only then in-person meetups. Examples and results: MuleSoft spins up ~40 meetups in 12 months and generated over $1M of community-created content in under two years; RingCentral tracks ~140 developer metrics and cuts first-app time from ~40 hours to minutes.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 4:53Purpose of developer relations
- 12:50Developers are people too
- 15:04Basic needs of developers
- 23:15Building community for developers
- 25:21Education beyond technology
- 29:01In-person activities and scaling
- 31:10Auditing and measuring programs
- 33:01Converting developers to advocates
- 34:07Q&A on documentation and community programs
related talks
52mMaslow’s Hierarchy of Needs for Java/Kotlin Developers
33mThe Power of Developer Communities
15mKeynote: Creating a Holistic Developer Experience
26mEnhance Developer Experience by community
26mScaling Better Software Delivery: A Framework for Dev Enablement Through DevRel and Outreach
19mDevelopers are all the same
46mForget Developer Platforms, Think Developer Productivity!
39mDeveloper Experience: How to Conquer the Hearts of Developers