# devrelshow ep 53 - Chris DeMars from TuxCare > [!info] Bib capsule > Frédéric Harper interviews Chris DeMars (senior/lead developer advocate, TuxCare) — 43 minutes, YouTube, 2026-07-17. Covers the definition of DevRel as bidirectional ambassadorship, TuxCare's end-of-life patching product line, DeMars's meetup-to-conference career on-ramp, and both hosts' shared position on AI as a bubble that won't replace the human core of the role. > [!question] Lingering Questions > - Does TuxCare actually measure DeMars's role by funnel contribution, roadmap influence, or content output — the episode never says? > - Does the "developer first" credibility gate hold for developer-adjacent audiences (designers, agency owners, no-code builders) the way it's asserted to hold for developers? > - How durable is the reported X/Twitter engagement recovery — both hosts flag it as days-old and anecdotal? > [!tip] Article Ideas > - "DevRel is a mission, not a team" as a reusable framing for the next internal review or job-ladder conversation, paired with the funnel + roadmap business case. > - A "developer-hat testing" ritual piece: rebuild a WordPress quickstart from your own docs once a sprint, log every discrepancy, file against docs/product backlogs. > [!link] Cross Reference > - [[3. Resources/MOCs/DevRel MOC]] — ambassador framing, friction-logging ritual, and the AI-proof-core claim all extend existing DevRel measurement/practice notes > - [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]] — DeMars's "advocate hat off, developer hat on" workflow is a named instance of this same practice > - [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] — DeMars cites "zero to hello world as quickly as possible" as the core external-facing goal > [!quote] Vocabulary > - **ELS (Endless Lifecycle Support)** — TuxCare's security-patching product for end-of-life apps/libraries/frameworks/OSes > - **"A patch while you figure out your patch"** — DeMars's tagline for TuxCare's positioning as a bridge, not a destination ## Author's thesis DevRel's durable definition is bidirectional ambassadorship — external friction removal (get developers to a working "hello world" fast) paired with an internal loop of rebuilding the product as a user and reporting findings back to docs and engineering. Credibility for the role comes from having shipped code; defensibility against AI automation comes from the human personality that is the actual product being sold. ## Key arguments (≤3) 1. **DevRel is a mission, not an org-chart team.** DeMars: "I frame Devril [DevRel, per auto-caption] not as a team but as a mission at the end of the day" — advocates are "ambassadors to the users and we are ambassadors to the product and the organization." Harper notes no guest in 53 prior episodes had used "ambassador" before. 2. **Internal advocacy is a repeatable ritual, not a vibe.** DeMars's concrete workflow: take off the advocate hat, put the developer hat on, scaffold a real app (e.g., Angular 15), run the product against it, walk the docs for discrepancies, report findings to docs and engineering as a user rather than a colleague. 3. **AI won't replace DevRel because the product is the person.** DeMars: "there's a people element to this that AI will never replace" — AI-written blog posts and generic videos strip out the personality that companies actually hire; he calls the broader AI sector "a bubble" that will pop, while still using Claude/ChatGPT/Gemini for brainstorming and scaffolding. ## Claim atoms ### DevRel operates as a mission, not a team > [!quote] ID:rw_pending > I frame Devril not as a team but as a mission at the end of the day ≈12:38 — DeMars on how he frames the role in interviews and daily work. Reframes org-chart placement as an operating stance; useful for budget and job-ladder conversations. **Tags**: #xref #aphorisms ### Developer advocates serve as ambassadors in both directions > [!quote] ID:rw_pending > we are ambassadors to the users and we are ambassadors to the product and the organization ≈07:16 — defining the senior developer advocate role at TuxCare. Names the invisible internal half of DevRel that outsiders rarely see. **Tags**: #xref ### Developer experience precedes advocacy credibility > [!quote] ID:rw_pending > have to be a developer first to be a developer advocate ≈10:01 — DeMars, before describing his developer-hat demo-testing workflow. The contested "gatekeeping" claim, held here as a success-probability argument rather than an exclusion rule. **Tags**: #xref ### TuxCare sells a bridge, not a destination > [!quote] ID:rw_pending > We keep you patched while you figure out your own migration path. ≈28:58 — followed by the tagline "a patch while you figure out your patch." A vendor explicitly planning for customers to eventually leave — an unusual, trust-building positioning. **Tags**: #xref #aphorisms ### Human connection is DevRel's AI-proof core > [!quote] ID:rw_pending > a people element to this that AI will never replace ≈37:10 — DeMars, immediately after "You have to care"; Harper extends it — personality is what companies actually hire. The episode's defensibility thesis for DevRel careers under AI automation. **Tags**: #xref #share ## Permanent candidates - **Internal advocacy needs a build-break-report ritual** — DeMars's developer-hat workflow (rebuild from your own docs, run the product, file the discrepancies) generalizes past this one guest and connects directly to the vault's existing friction-logging and time-to-hello-world notes. Promoted below. - The "mission not team" framing and the AI-proof-human-core claim are both aphoristic and reusable but thinner as standalone claims than the ritual — held as claim atoms only, not promoted separately this pass. ## Processing checklist - [x] Ported from the existing 18-section deep-read (Refactor Appendix already present in Readwise notes field) - [ ] Verify DeMars's episode-53 "first guest to say ambassador" claim isn't just a memory slip (would require checking the full 53-episode catalog — low priority) - [x] Connect into the relevant MOC — [[3. Resources/MOCs/DevRel MOC]] - [ ] Watch for whether the reported X/Twitter engagement recovery shows up anywhere else in the vault's DevRel intake over the following month ## Links - [[3. Resources/MOCs/DevRel MOC]] — direct topical fit: DevRel definition, internal-advocacy practice, and AI-vs-DevRel positioning - [[3. Resources/Readwise/Articles/Devrelshow Episode 53 - Chris DeMars From TuxCare|devrelshow episode 53 - Chris DeMars from TuxCare]] — source document