Ignite: On Being A Developer Advocate
summary
Developer advocacy trades years of on‑call burnout for a role that uses MongoDB, cloud platforms, blogging and breaking things to build reproducible demos, write how‑tos and recruit community contributors. It emphasizes community building and networks over sales metrics, shows concrete technical choices and outcomes, and cites a fandom example where McDonald’s reorders 30 million packets of Szechuan sauce as a measurable effect of advocacy-driven demand.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:19And I dealt with burnout.
- 0:49Time to move in a new direction
- 1:04What about SALES? ?
- 1:19What about Support?
- 1:34OK, so what was the next step?
- 2:04DEVELOPER ADVOCACY
- 2:34Using skills learned over time...
- 2:49New skills, community building
- 3:04Analogy time folks.
- 3:19Fandom... Begat Advocacy.
- 3:49The fans left their homes...
- 4:34Tools and info is the sauce?
related talks
06mIgnite - A DevOps Necessary Evil: Marketing
35mBuilding Effective Developer Experience
29mThe new OSS community: Enabling for advocates not customers
20mWhy does an API Platform need developer evangelists?
19mDevelopers are all the same
49mKeynote - How To Be A Developer and Other Lies We Tell Ourselves with Mario Munoz
56mWhat Developers Want!
39mDeveloper Experience: How to Conquer the Hearts of Developers