The developer relations bill of rights
summary
Argues for a concrete, adoptable standard for developer relations: a 10 community-sourced principles "Dev Rel Bill of Rights" that demands clear business goals, a defined org home, a structured product-feedback process, measurable tools and metrics, explicit ethics and inclusion budgets, and separation from sales engineering. Uses Fog Creek/Glitch, Stack Overflow and Trello as context, reports publishing the list and getting community feedback, and claims the checklist already helps teams win budget, influence product, and keep devrel roles sustainable.
AI-written summary · about
chapters (16)
- 0:00Early career and inspiration
- 3:54Rise of developer evangelism
- 8:05Defining developer relations
- 12:39Developer culture and values
- 16:12Introducing the Developer Relations Bill of Rights
- 17:16Clear business goals
- 17:59Organizational placement
- 19:25Impact on product and platform
- 21:07Marketing and dev rel alignment
- 22:31Right tools and metrics
- 24:19Ethical and social guidelines
- 24:40Inclusive community support
- 25:42Distinction from sales engineering
- 26:27Professional development
- 27:11Peer community connection
- 28:59Future of developer relations
related talks
32mThe Four Pillars of Support in Developer Relations
33mThe Strategic Power of DevRel: From Community to Business Impact
41mBut what is a DevRel for?
28mClosing Keynote: A Bill of Rights for Testers
30mDevRel is a lie
01h 10mLife as a DevRel Panel
46mHow to get hired in DevRel: roundtable with industry leaders
53mDeveloper Communities are just like coffee shops