The Four Pillars of Support in Developer Relations
summary
Defines four concrete support areas and what to do in each: four pillars are individuals, maintainers, projects and community. Recommends actionable steps — content, contributor guidelines, weekly meetings and a formal mentorship program for onboarding; designate two maintainers to prevent burnout; act as the hub of the wheel inside the company to route feedback to product, recruiting and engineering; publish docs and a code of conduct; track metrics and community-focused CRM signals to prove DevRel value and sustain funding.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:25Who we are and our roles
- 2:50Defining support and developer relations
- 4:15Supporting individuals in communities
- 8:32Supporting maintainers to prevent burnout
- 12:26Supporting projects and teams
- 15:12Supporting broader communities
- 19:52Summary of four pillars
- 23:27Resources and closing remarks
- 24:29Q&A on developer relations uniqueness
- 27:46Q&A on devrel's ultimate goal
- 30:59Final Q&A and wrap-up
related talks
27mDevRel Leadership: all the pieces matter
30mThe developer relations bill of rights
22mReactive versus proactive strategies for developer relations
33mThe Strategic Power of DevRel: From Community to Business Impact
24mBuilding Trust: Developer Relations Secrets for API Success
01h 10mLife as a DevRel Panel
41mBut what is a DevRel for?
28mBuilding Thriving Communities in Platform Engineering: Collaboration, Innovation, and Growth