What it’s like to be a Developer (and) Advocate?
summary
Explains how one person mixes fullstack coding with community work using concrete outputs: maintains Next modules (next security, next image), helps produce the state of vuejs report 2025, builds internal tools and a proof‑of‑concept called N0, runs meetups and workshops, and measures time as a 60/40 split between development and advocacy. Claims one article about ESLint rules reached ~50,000 views, argues the role is a jack of all trades and shows practical ways to keep coding while doing outreach.
AI-written summary · about
chapters (8)
- 0:00Developer advocacy intro
- 3:19What a developer advocate does daily
- 8:38Balancing dev and advocacy
- 11:52Starting as a dev advocate
- 12:56Staying connected with tech
- 13:38Q&A: Rewarding aspects
- 16:12Q&A: Creating dev content
- 19:23Q&A: AI dev limits
related talks
48mThe community power in the developers life
35mAn introduction to developer experience, and the role of a documentarian
16mWhat writing about frontend dev taught me about communicating with the world
34mNew to Front End Dev? Get Rocking With Vue.js
20mFrom Code to Community: Making a Difference as an Advocate
30mScaling external advocacy without losing your soul
16mThe job of my dreams
40mForging Your Career in DevRel Advocate to Exec