# The DevRel Show episode 53 — Chris DeMars from TuxCare ## 🗂️ Triage — annotated highlights surfaced > [!note]- Cross Reference > - **DevRel operates as a mission, not a team** — reframes org-chart placement as an operating stance; ammunition for budget and job-ladder conversations. #xref > - **Advocates are ambassadors in both directions** — names the invisible internal half of the job that funnel-only DevRel metrics miss. #xref > - **Human connection is DevRel's AI-proof core** — the defensibility thesis for the discipline as AI commoditizes content production. #xref ## 🧭 Bib capsule Frédéric Harper (host) with Chris DeMars (TuxCare), *The DevRel Show* episode 53, YouTube, 2026 — https://www.youtube.com/watch?v=cASKKadsefo ## 🧠 Author's thesis (Adler Q1+Q2) Developer relations is bidirectional ambassadorship run as a mission, not a team: externally you get developers from zero to a working "hello world" and remove friction, and internally you re-enter the developer's shoes — build a real demo, run your own product, audit the docs — then carry the pain points back to engineering as a user. Credibility comes from having shipped as a developer first; defensibility against AI comes from the human personality companies actually hire, since AI-written content strips out the specific voice that is the real product. ## 🧩 Key arguments - Internal advocacy is a repeatable ritual (build with your own product, break it, report discrepancies), not just empathy — that's what makes "voice of the developer" auditable. - The DevRel business case is funnel plus roadmap intelligence: advocacy fills the top of the funnel and routes field objections ("they won't use it because XYZ") into the roadmap. - AI is useful for brainstorming and scaffolding but can't replace the human relationship core; DeMars calls the broader AI moment a bubble and predicts DevRel grows more valuable as other touchpoints dehumanize. ## 🗒️ Notes — Literature atoms ### DevRel operates as a mission, not a team > [!quote] > I frame Devril not as a team but as a mission at the end of the day - **Where**: ≈12:38 ("Devril" is the auto-caption's rendering of DevRel) - **Why**: Turns an org-chart line item into an operating stance — a frame that survives reorgs and budget reviews. ### Developer advocates serve as ambassadors in both directions > [!quote] > we are ambassadors to the users and we are ambassadors to the product and the organization - **Where**: ≈07:16, defining the senior developer advocate role at TuxCare - **Why**: Names the internal half of DevRel; Harper notes no guest in 53 episodes had used "ambassador" before. ### Developer experience precedes advocacy credibility > [!quote] > have to be a developer first to be a developer advocate - **Where**: ≈10:01, before describing the developer-hat demo-testing workflow - **Why**: The contested "gatekeeping" claim, held as a success-probability argument rather than an exclusion rule. ### Human connection is DevRel's AI-proof core > [!quote] > a people element to this that AI will never replace - **Where**: ≈37:10, right after "You have to care" - **Why**: The episode's defensibility thesis — companies hire a specific person's voice, which generic AI output cannot supply. ## 🔖 Permanent candidates - Internal advocacy needs a build-break-report ritual — The voice of the developer only counts inside a company when it arrives as a repeatable ritual: rebuild from your own docs, run the product, file the discrepancies. ## Links - [[DevRel MOC]] — home MOC; this episode supplies a portable definition (bidirectional ambassadorship as mission) and the funnel-plus-roadmap business case - [[Balancing Internal and External Activities in DevRel]] — directly extends the "ambassadors in both directions" claim into how advocates split internal versus external effort - [[The Developer Advocate's Guide to Addressing Product Friction]] — the friction-removal and developer-hat testing loop DeMars describes as the internal advocacy ritual - [[Friction Logging Is the DevRel Equivalent of Code Review]] — names the repeatable audit practice behind DeMars's build-break-report account of internal advocacy ## ✅ Processing checklist - [x] Claim atoms carried from deep-read analysis - [ ] Permanent candidates reviewed for promotion - [ ] Version History Diff check