Devrelshow Episode 53 - Chris DeMars From TuxCare

Devrelshow Episode 53 - Chris DeMars From TuxCare ![rw-book-cover](https://i.ytimg.com/vi/cASKKadsefo/sddefault.jpg?v=6a55271d) 🔗 **Source:** [Devrelshow Episode 53 - Chris DeMars From TuxCare](https://www.youtube.com/watch?v=cASKKadsefo) > [!note]+ Document Notes > tags: [developer-relations, developer-advocacy, software-supply-chain-security, ai-and-devrel, community-building] > author: Frédéric Harper > source: The DevRel Show (Frédéric Harper, YouTube) > reference: https://www.youtube.com/watch?v=cASKKadsefo > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: The DevRel Show episode 53 — Chris DeMars from TuxCare >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [The DevRel Show episode 53 (video)](https://www.youtube.com/watch?v=cASKKadsefo) - [TuxCare](https://tuxcare.com) - [DevRelCon New York](https://developerrelations.com/devrelcon) - [CodeMash conference](https://codemash.org) ## 📝 Summary - Frédéric Harper hosts Chris DeMars, senior/lead developer advocate at TuxCare, for a 43-minute conversation on what the DevRel role actually is, how internal advocacy works day to day, TuxCare's product line, career paths into DevRel, and whether AI threatens the discipline. - Why it matters: two veteran practitioners converge on a shared definition of DevRel — bidirectional ambassadorship — and articulate a defensible position on AI: the human-relationship core of the job resists automation even as content production gets commoditized. - Key stakeholders: DevRel practitioners, DevRel hiring managers, developer-tool companies (TuxCare sells end-of-life security patching), and communities on Twitter/X, where both hosts report engagement suddenly recovering after an algorithm change. - Risks and tradeoffs: DeMars publicly calls AI "a bubble" that will pop — a contrarian stance for a security-company advocate; the episode also leans on anecdote (Twitter engagement anecdotes, personal career stories) rather than data. - Bottom line: DevRel is a mission, not a team — credibility comes from being a developer first, advocating in both directions, and keeping the human element that AI can't replicate. ## 📖 Main Content - **Role definition.** DeMars defines senior developer advocacy at TuxCare as fostering community relationships, getting developers "from zero to hello world as quickly as possible," removing bottlenecks, and cultivating community internally. The load-bearing concept: advocates are ambassadors in both directions — to the users and to the product and organization. Harper notes this is the first time in 53 episodes a guest has used the word "ambassador," and both agree it captures the internal half of the job that outsiders rarely see. - **Internal advocacy as a workflow, not a vibe.** DeMars describes a concrete practice: take off the advocate hat, put the front-end developer hat back on, scaffold a real app (e.g., Angular 15), run TuxCare's product against it, walk the docs looking for discrepancies, then take findings back to the docs and engineering teams (his team owns ELS for JavaScript — Angular, AngularJS, Nuxt, Vue). This "developer-hat testing" is how the voice of the developer becomes actionable input rather than sentiment. - **Mission framing.** DeMars frames DevRel "not as a team but as a mission" — on paper it's a team, but the operating stance is a mission of ambassadorship across the developer journey. Harper connects this to the business case: even without pitching the product, good advocacy fills the top of the funnel and feeds field intelligence into the roadmap ("they won't use our product because XYZ"). - **Credibility gate.** Both agree you "have to be a developer first to be a developer advocate" — not gatekeeping the title, but a prediction that people without shipping experience struggle to connect with developer audiences. Contested point: Harper acknowledges a prior debate where someone accused this stance of gatekeeping; he holds it as a success-probability claim, not an exclusion rule. - **What TuxCare is.** Not a tuxedo-cleaning company (a running booth joke). Three product pillars: (1) Endless Lifecycle Support (ELS) — security patching (CVE fixes) for end-of-life applications, libraries, frameworks, and OSes: Angular, AngularJS, Nuxt (Nuxt 3 support just shipped), Bootstrap, Java, PHP, .NET; (2) KernelCare — live, rebootless patching for 60+ Linux distributions, plus enterprise support for AlmaLinux, which TuxCare created; (3) SecureChain (released May of this year) — a vetted, malware-scanned "dome of armor" around package ecosystems (npm, PyPI, Maven Central) covering pre- and post-end-of-life supply-chain exposure. Positioning aphorism: "a patch while you figure out your patch" — they keep you patched while you plan your own migration, and explicitly don't want customers to stay forever. - **Twitter/X engagement recovery.** A long middle segment: both report that after a recent algorithm change, engagement and visibility of personal accounts abruptly returned after roughly two years of "posting into the void" — Harper compares it to "the blip" in the Marvel movies. They predict a positive feedback cycle (fun returns → time spent returns → fun returns) and expect corporate and personal accounts promoting blog posts, webinars, and streams to benefit. Uncertainty: this is anecdotal, days-old, and both self-describe as cynical about whether it lasts. - **Path into DevRel.** DeMars: extrovert, front-end developer in Detroit in the early 2010s where the meetup scene was thin (Joomla, Drupal, a Java user group); later found Refresh Detroit and Girl Develop It Detroit, became a TA, then a meetup speaker, then submitted to a conference in 2016 (accepted, but his employer refused the time off), then spoke at CodeMash 2017, and did about 30 talks in 2018. Pattern both agree on: nearly everyone does DevRel-shaped things for free before discovering they can be paid for it. - **AI and DevRel.** DeMars has personally lost a job to AI once. He uses Claude, ChatGPT, and Gemini for brainstorming and scaffolding, but says AI is "not the end all be all" and calls the whole thing a bubble that will pop — flagging he may piss people off. Both draw the same line: DevRel is human-to-human connection; AI-written blog posts and generic videos strip out the personality that is the actual product ("people hire you because you're you"). Harper reports his new manager explicitly affirmed AI won't replace the role. Both predict DevRel becomes more important as AI removes humans from other touchpoints. ## 🗒️ Notes #### ⏱️ [00:00:31](https://www.youtube.com/watch?v=cASKKadsefo&t=31) Cold open — wildfire smoke small talk - Harper (Quebec) apologizes for Canadian wildfire smoke reaching DeMars (Detroit area); notes it's been recurring every summer for three or four years. - Harper floats poor forest management (controlled burns not done) plus climate as causes; expects it to persist "for the remaining years of the rest of our life." #### ⏱️ [00:02:31](https://www.youtube.com/watch?v=cASKKadsefo&t=151) Who is Chris DeMars - Developer advocate "lead, senior, whatever" at TuxCare; also a competitive bass angler who fishes for money. - Builds micro-communities around hobbies: paintball, Bigfoot chasing, UFOs, paranormal conventions. - Harper explains he does no pre-interview prep on purpose — he wants the discussion natural. #### ⏱️ [00:04:30](https://www.youtube.com/watch?v=cASKKadsefo&t=270) The "Salt n Burn" handle - Twitter handle comes from the TV show Supernatural: you salt and burn the bones to destroy a ghost. - He opens conference talks with the reference as an audience-connection hook. #### ⏱️ [00:06:28](https://www.youtube.com/watch?v=cASKKadsefo&t=388) What senior developer advocate at TuxCare means - Foster community relationships; get developers from zero to hello world fast; remove bottlenecks; cultivate internal community. - Key quote: "we are ambassadors to the users and we are ambassadors to the product and the organization." - Harper: the visible half (talks, streams, webinars, blog posts) is only part; internal relations are equally the job. #### ⏱️ [00:08:50](https://www.youtube.com/watch?v=cASKKadsefo&t=530) How internal advocacy works in practice - DeMars works with docs and the ELS-for-JavaScript engineering team (Angular, AngularJS, Nuxt, Vue; also Java, Spring, back end). - Workflow: advocate hat off, developer hat on → scaffold an Angular 15 demo → run the product against real vulnerabilities → walk the docs for discrepancies → report back as "the developer having to use that product." - "You have to be a developer first to be a developer advocate" — 30 years as a developer behind it. #### ⏱️ [00:12:38](https://www.youtube.com/watch?v=cASKKadsefo&t=758) DevRel as mission, not team - "I frame Devril not as a team but as a mission" — on paper a team, operationally a mission of ambassadorship across the developer journey. - Mentions Joey deVilla (accordion and all) from the previous day's TuxCare stream. #### ⏱️ [00:14:15](https://www.youtube.com/watch?v=cASKKadsefo&t=855) The business case — funnel and roadmap - Harper: even without pitching, advocacy fills the top of the funnel with potential users. - Field feedback either changes the roadmap or lets you tell the community "it's already on the roadmap — we're two steps ahead of you." DeMars: both moves are extremely important. - Harper started DevRel with Joey deVilla at Microsoft Canada ~14-15 years ago; plug for DevRelCon New York the following week. #### ⏱️ [00:16:33](https://www.youtube.com/watch?v=cASKKadsefo&t=993) Twitter engagement comes back - Both report a sudden return of engagement after an algorithm change days earlier: Harper sees friends' faces again; DeMars woke up to 20+ notifications, "haven't seen that in years." - Harper compares the return to "the blip" in the Marvel movies; admits LinkedIn had become his de facto social network, "which for me it's a problem." - Harper pays for Twitter mainly to stream the show there — it has always out-drawn YouTube for this show. #### ⏱️ [00:22:19](https://www.youtube.com/watch?v=cASKKadsefo&t=1339) Prediction — corporate and personal reach improves - DeMars: TuxCare's account and his own saw little engagement on work content; expects the algorithm change to lift both corporate and personal accounts. - Harper: a positive cycle — Twitter fun again → more time on Twitter → Twitter fun again. #### ⏱️ [00:23:30](https://www.youtube.com/watch?v=cASKKadsefo&t=1410) What TuxCare is - Booth joke: "we're a Tuxedo Cleaning Company" — a prospect glitched for 20 seconds staring at the logo. - ELS: endless lifecycle support for end-of-life apps, libraries, frameworks, OSes — vendor support ends, TuxCare keeps patching CVEs; you swap their dependencies in for yours. - Coverage: Angular, AngularJS, Nuxt (Nuxt 3 just added), Bootstrap (and the 960 grid system era nod), Java, PHP, .NET. - KernelCare: live rebootless patching for 60+ Linux distributions, patched "within nanoseconds as long as a kernel is available"; TuxCare created AlmaLinux and sells its enterprise support. - SecureChain (May release): vetted, malware-scanned packages for npm/PyPI/Maven Central — supply-chain protection before and after end of life. #### ⏱️ [00:28:12](https://www.youtube.com/watch?v=cASKKadsefo&t=1692) Why it matters now — and the tagline - Harper: vibe coding and unreviewed AI output make this product category more important; sometimes now isn't the right time to upgrade, and unpatched EOL software is an open door. - DeMars: upgrades cost people-time and break things; "We keep you patched while you figure out your own migration path" — "a patch while you figure out your patch." - Aside: Harper interviewed for the same TuxCare role DeMars won; no hard feelings. #### ⏱️ [00:29:23](https://www.youtube.com/watch?v=cASKKadsefo&t=1763) TuxCare live stream — open guest call - Every Wednesday, 11 a.m. Eastern; DM @saltnburn on Twitter to book; booking link provided; guests wanted through end of year. - Broadcasts to Twitch, TuxCare YouTube, Facebook, his Twitter, and LinkedIn (corporate Twitter account has issues); guests get the video afterward to promote. - Harper was a past guest and demoed TinyMCE — rare space for an advocate to actually pitch their product. #### ⏱️ [00:31:43](https://www.youtube.com/watch?v=cASKKadsefo&t=1903) Path into DevRel - Early-2010s Detroit meetup scene was thin (Joomla, Drupal, a Java user group) — nothing for a front-end developer. - A non-tech friend told him to recheck Meetup: found Refresh Detroit and Girl Develop It Detroit → TA → meetup speaker → conference CFP. - 2016: accepted at his first conference but his employer refused the time off; he later left. 2017: two talks at CodeMash; five or six talks that year; ~30 talks in 2018 not counting meetups. - Ingredients he names: extrovert, wants to teach, background in writing and speaking. #### ⏱️ [00:37:34](https://www.youtube.com/watch?v=cASKKadsefo&t=2254) AI and DevRel - DeMars lost a job to AI at one point in his career. He still thinks "this whole AI thing is a bubble" that will pop. - He uses Claude, ChatGPT, and Gemini for brainstorming and scaffolding but says it's "not the end all be all." - Shared line in the sand: "there's a people element to this that AI will never replace." AI-written blog posts and generic videos remove the personality that companies actually hire — "people hire you because you're you." - Harper's new manager explicitly affirmed the team won't be replaced by AI; both predict DevRel grows more important as other touchpoints dehumanize. #### ⏱️ [00:41:07](https://www.youtube.com/watch?v=cASKKadsefo&t=2467) Wrap-up and plugs - Follow @saltnburn and TuxCare; tuxcare.com; Wednesday stream; new breaking-news cybersecurity stream "The Week Link" with "senior news reporter Vance Patchley" (a character bit). - DeMars upcoming: Chain React lightning talk on React Native/JavaScript security, Black Hat US in Vegas, Commit Your Code. - Harper: DevRelCon New York next week; next episode's guest is from YugabyteDB. ## 📚 References - [The DevRel Show episode 53 — Chris DeMars from TuxCare](https://www.youtube.com/watch?v=cASKKadsefo) - [TuxCare — Endless Lifecycle Support, KernelCare, SecureChain](https://tuxcare.com) - [AlmaLinux OS](https://almalinux.org) - [CodeMash](https://codemash.org) - [Girl Develop It](https://girldevelopit.com) - [Chain React conference](https://chainreactconf.com) - [Black Hat USA](https://blackhat.com) ## 🗣️ Paraphrase - DeMars's core claim: the developer advocate job is bidirectional ambassadorship. Externally you get developers to a working "hello world" fast and remove friction; internally you re-enter the developer's shoes — build a real demo, run the product, audit the docs — and carry the resulting pain points back to engineering and docs teams as a user, not a colleague. The title says "team"; the operating model is a mission. - On AI: he's pragmatic, not hostile — AI tools are good brainstorming and scaffolding aids — but he believes the sector is a bubble and that the irreplaceable core of DevRel is human personality and relationships. Companies don't buy generic content; they buy a specific person's voice and credibility. Both host and guest predict the human-facing role appreciates in value as AI strips humans out of other channels. ## 📰 Newsletter - DevRel definition worth stealing: Chris DeMars (TuxCare) calls advocates "ambassadors to the users and ambassadors to the product" — a tidy frame for explaining to WordPress stakeholders why community work and internal product feedback are the same job. Watch [episode 53 of The DevRel Show](https://www.youtube.com/watch?v=cASKKadsefo). - If your agency still runs end-of-life PHP or an ancient Bootstrap front end, TuxCare's "patch while you figure out your patch" model (ELS + the new SecureChain supply-chain product) is an interesting stopgap pattern — the WordPress parallel is every site stuck on an unsupported major version. - Career note for aspiring advocates: DeMars's path ran meetup attendee → TA → meetup speaker → CodeMash → ~30 talks in a year. The ladder still works; WordCamps and meetups remain the on-ramp. ## ✅ Action Items #### DevRel - Developer advocacy: adopt the "developer-hat testing" ritual — once a sprint, scaffold a fresh WordPress plugin or block theme from your own docs/quickstarts, log every discrepancy, and file it against the docs and product backlogs the way DeMars does with Angular demos. - Developer advocacy: steal the "mission, not team" framing for the next internal review or job-ladder conversation; pair it with the funnel/roadmap business case (field feedback → roadmap, or "already on the roadmap — we're two steps ahead"). - Education: turn the "zero to hello world as quickly as possible" metric into an actual measurement — time a newcomer from docs landing page to first rendered block; treat regressions like perf regressions. - Developer experience: audit one quickstart for the "discrepancy walk" DeMars describes — run every command verbatim, note where docs and product disagree. - Developer marketing: revisit X/Twitter distribution — both hosts report personal-account engagement recovering post-algorithm-change; test resharing evergreen posts there for two weeks and compare against LinkedIn before reallocating effort. - Community management: DeMars books stream guests via a public DM-me call plus a booking link, and hands guests the finished video for their own channels — copy that guest-pipeline mechanic for any WordPress stream or podcast. - Internal/external: schedule a standing sync with the product team to route conference-floor objections ("they won't use it because XYZ") into the roadmap. #### OSPO - Policy & Governance: not applicable to this source — the episode doesn't touch open source program governance. - License Compliance: not applicable to this source — no licensing discussion. - Security Management: evaluate the end-of-life patching pattern (TuxCare ELS/KernelCare-style vendors) as an interim control for legacy dependencies; document when "patch while you migrate" is acceptable versus forced upgrade. - Software Inventory: SecureChain's pitch (vetted, malware-scanned npm/PyPI/Maven mirrors) is a prompt to check whether your SBOM flags end-of-life packages at all. - Developer Support / Community Engagement / Strategic Alignment: no direct actions from this source. #### Community - Maintainers: the AlmaLinux aside (created by TuxCare, then "took its own path") is a case study in vendor-born projects gaining independent governance. - Contributors: republish DeMars's on-ramp (attend → TA → meetup talk → conference CFP) as a mentorship path for first-time WordPress speakers. - Sponsors: not applicable to this source — no sponsorship discussion. - Ecosystem: supply-chain vetting for package ecosystems is directly relevant to plugin/theme directory trust conversations. #### WordPress - Core: not applicable to this source — no WordPress core content. - Core Performance: not applicable to this source. - Core AI: DeMars's line — AI for brainstorming/scaffolding, never for replacing the human voice — is a usable guardrail for AI-assisted WordPress content and docs work. - **Core Program Team:** not applicable to this source. - Community: WordCamp/meetup organizers can mirror the Detroit lesson — visible, niche-specific meetups (a front-end dev found nothing relevant and disengaged for a year) determine who ever enters the contributor funnel. - Training: model a "first talk" learning path on the TA → meetup → conference ladder. - Marketing: retest X/Twitter reach for WordPress announcements given the reported algorithm change. - Support / Design / Documentation: apply the docs-discrepancy walk to DevHub quickstarts. - Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse, Themes, Plugins: not applicable to this source — no episode content maps to these teams; Plugins excepted insofar as supply-chain vetting (SecureChain) parallels plugin provenance checks. #### The WPCC - Programs / Projects / Funding experiments: not applicable to this source — no funding or fellowship content. ### FAIR - Technical independence: SecureChain's vetted-mirror model is a concrete reference point for FAIR's provenance and signature-check goals for package distribution. - Policies and covenants: not applicable to this source. - Productized governance artifacts: not applicable to this source. ## 🧪 Hypotheses - H1: DevRel programs that run structured "developer-hat testing" (advocates rebuilding from their own docs) surface more doc and DX defects per quarter than programs relying on community bug reports alone. - H2: Advocates with prior shipping experience as developers achieve higher audience trust scores and content engagement than advocates without it, controlling for tenure. - H3: The reported X/Twitter algorithm change produces a measurable, sustained (>90 day) lift in personal-account engagement for developer advocates versus the prior twelve-month baseline. - H4: Framing DevRel internally as a "mission" with funnel and roadmap outcomes correlates with better budget survival in downturns than framing it as a content team. - H5: Demand for end-of-life patching services (ELS/KernelCare-style) rises with the volume of AI-generated, lightly reviewed code entering production. ### 📊 Methodology - H1: A/B two quarters within one DevRel team — one with a scheduled docs-rebuild ritual, one without; count filed defects and time-to-fix. - H2: Survey developer audiences on advocate credibility; regress on advocates' verified engineering background; supplement with engagement analytics. - H3: Pull per-account engagement time series (impressions, replies, likes) for a panel of ~50 DevRel accounts across the algorithm-change date; interrupted time-series analysis. - H4: Comparative case interviews with DevRel leaders through the 2023-2025 layoff cycles; code for framing language versus budget outcomes. - H5: Track EOL-patching vendor revenue/customer counts against indices of AI coding-assistant adoption; lagged correlation. ### ❓ Questions - What metrics does TuxCare actually use to evaluate DeMars's role — funnel contribution, roadmap influence, or content output? - Does the "developer first" credibility gate hold for developer-adjacent audiences (designers, agency owners, no-code builders) that WordPress DevRel also serves? - How durable is the X/Twitter engagement recovery, and does it extend to corporate accounts as DeMars predicts? - Where is the line between AI as scaffolding aid and AI eroding the personal voice that both hosts say is the product? ### 🔮 Future Research - Longitudinal data on where developer communities actually re-aggregated (X, LinkedIn, Bluesky, Discord) after 2023-2026 platform churn — this episode is a single anecdotal data point. - Whether supply-chain "vetted mirror" products (SecureChain and competitors) measurably reduce incident rates versus SCA scanning alone. - Systematic study of DevRel career on-ramps: what fraction still comes through the meetup → conference ladder versus content-first (YouTube/streaming) paths. ### 💡 Implications - Practice: internal advocacy needs a repeatable ritual (build, break, report), not just empathy — that's what makes "voice of the developer" auditable. - Policy: organizations running EOL software have a middle option between risky stasis and rushed migration; security policy should name it and bound it in time. - Security: AI-accelerated, under-reviewed code increases the value of vetted dependency channels and post-EOL patching. - Education: speaker pipelines still start at meetups; employers that refuse conference time off (as DeMars's did in 2016) leak talent. - Funding models: DevRel justified as funnel + roadmap intelligence is easier to defend than DevRel justified as reach. ### 🧠 Learning Styles Assessment - Reading level estimate: conversational transcript, roughly Flesch-Kincaid grade 6-7 (short spoken clauses, informal register, some unexpanded jargon: CVE, ELS, EOL, supply chain). #### 👀 Visual learners - Present: talking-head video only; no slides, diagrams, or screen shares. - Improve: product-architecture diagram for ELS/KernelCare/SecureChain; a timeline graphic of DeMars's meetup-to-conference ladder. #### 🔊 Aural learners - Present: strong — it's a live conversational podcast with two engaged speakers. - Improve: a 2-3 minute audio recap of the three core takeaways at the end. #### 🗣️ Verbal learners - Present: memorable coinages ("ambassadors," "mission not team," "a patch while you figure out your patch"). - Improve: on-screen definitions for CVE, end-of-life, and supply chain when first used. #### 🧩 Kinesthetic learners - Present: DeMars describes a hands-on demo workflow but nothing is shown. - Improve: a companion repo showing the Angular demo + patched-dependency swap; a "try SecureChain in 10 minutes" lab. #### 🧠 Logical learners - Present: clear causal argument for the funnel/roadmap business case. - Improve: any numbers at all — engagement stats, patch counts, distro coverage table. #### 🧑‍🤝‍🧑 Social learners - Present: live chat acknowledged on air ("Hi, Dan"); open guest call with a concrete DM path. - Improve: a discussion prompt or community thread per episode. #### 🧘‍♀️ Solitary learners - Present: full transcript available for self-paced review. - Improve: chaptered timestamps and a written summary in the description. #### 🌿 Naturalistic learners - Present: the wildfire opening ties tech life to environment, incidentally. - Improve: lifecycle framing (software "end of life" as ecosystem succession) is a natural analogy left unused. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: YouTube page structure; transcript exists (this analysis is built from it). - Improve: publish a cleaned, speaker-labeled transcript — the auto-captions misrender "DevRel" as "Devril/Devil" throughout, which corrupts both captions and search. #### Keyboard navigation - Present: standard YouTube player controls. - Improve: chapter markers would make keyboard seeking meaningful. #### Contrast and readability - Not directly assessable from transcript; standard webcam video, no on-screen text reported. #### Text resizing and reflow - Present: YouTube caption sizing applies. - Improve: nothing source-specific. #### Media and captions - Present: auto-generated captions only, with significant error rate on domain terms (Devril/Devil, Tuxare/Toxare, Nux for Nuxt, nanconds). - Improve: human-corrected captions and a downloadable transcript; profanity is bleeped but bracketed artifacts remain in captions. #### Forms and interactions - Not applicable to this source — no interactive elements beyond the platform player. #### Standards reference - Caption accuracy gaps map to WCAG 2.2 AA 1.2.2 (Captions, Prerecorded) and 1.2.3/1.2.5 (Media Alternative/Audio Description not provided). ### 🌍 DEIB Assessment #### Cultural breadth - Present: cross-border conversation (Quebec/Detroit), US and Canadian conference references. - Improve: examples skew North American; global meetup and conference on-ramps go unmentioned. #### Inclusive language - Present: casual, warm register; "beautiful people" greeting; guest-defined self-description. - Improve: heavy unexplained jargon (CVE, ELS, CFP) assumes insider status; occasional profanity (bleeped) narrows workplace shareability. #### Neurodiversity support - Present: conversational and story-driven. - Improve: no chapters, no agenda, long unsegmented Twitter tangent — structure would help listeners who need predictable formats. #### Representation - Present: DeMars credits Girl Develop It Detroit as a formative community; guest call is open to anyone. - Improve: two-male-host format is the norm for this show's episode sample; deliberate guest diversity would broaden voices. #### Psychological safety - Present: host normalizes disagreement ("friendly discussion and argue"); DeMars flags his AI-bubble take as potentially unpopular without attacking anyone. - Improve: nothing notable; tone is respectful throughout. ### ✅ Logical Validity #### Strong reasoning - Analogical strength: "a patch while you figure out your patch" (≈28:58) compresses a real tradeoff — migration cost versus exposure window — into an accurate model of the product's role. - Causal chain: advocacy → community trust → funnel fill + roadmap intelligence → business value (≈14:15) is explicit, mechanistic, and falsifiable. - Inductive: the meetup-to-conference career ladder is supported by two independent first-person histories that match (≈32:07-35:14). #### Fallacies - Hasty generalization: "Twitter is back" (≈17:19-23:30) rests on a few days of personal notification counts; fix — hold the claim until 90-day engagement data exists. - Unsupported assertion: "this whole AI thing is a bubble, and at some point it's going to pop, and we know it's going to pop" (≈38:02) — "we know" smuggles certainty; fix — state it as a belief with named indicators to watch. - Mild self-selection: "we're all good humans... the ones that are not usually don't stay long" (≈36:25) — survivorship framing of the profession; fix — acknowledge retention pressures also remove good people. #### Tone of voice - Warm, profane-casual, mutually affirming ("I love that," "100%"); self-deprecating (Harper on his word fumbles); candid about industry doubts (AI bubble, Twitter cynicism). ### 🛡️ DARVO Analysis - Deny: none observed — both speakers volunteer their own losses (Harper lost the TuxCare job to DeMars; DeMars lost a job to AI) without minimization. - Attack: none — DeMars pre-apologizes to AI practitioners rather than attacking them. - Reverse victim/offender: not applicable to this source — a collegial interview with no accusations or grievance dynamics to invert. ## 🎯 Conclusion - Bottom line: DevRel's durable definition is bidirectional ambassadorship run as a mission — external friction removal plus a concrete internal loop of building with your own product and docs and reporting back as a user. Credibility comes from developer experience; defensibility against AI comes from the human personality that is the actual product. - Next steps for readers: install a docs-rebuild ritual on your own product, measure zero-to-hello-world time, route field objections into the roadmap with a standing product sync, and retest X/Twitter distribution against LinkedIn now that engagement has reportedly recovered. ## 🔄 Refactor Appendix — devrelshow episode 53 - Chris DeMars from TuxCare > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) ### [H1] 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 **Context & use**: - ≈12:38 — DeMars on how he frames the role in interviews and daily work ("Devril" is the auto-caption's rendering of DevRel). - Reframes org-chart placement as operating stance; useful for budget and job-ladder conversations. **Tags**: #xref #aphorisms  ### [H2] 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 **Context & use**: - ≈07:16 — defining the senior developer advocate role at TuxCare. - Names the invisible internal half of DevRel; Harper says no guest in 53 episodes used "ambassador" before. **Tags**: #xref  ### [H3] Developer experience precedes advocacy credibility > [!quote] ID:rw_pending > have to be a developer first to be a developer advocate **Context & use**: - ≈10:01 — DeMars, before describing his developer-hat demo-testing workflow. - The contested "gatekeeping" claim, held here as a success-probability argument, not an exclusion rule. **Tags**: #xref  ### [H4] TuxCare sells a bridge, not a destination > [!quote] ID:rw_pending > We keep you patched while you figure out your own migration path. **Context & use**: - ≈28:58 — followed by the tagline "a patch while you figure out your patch." - Model positioning: a vendor that explicitly plans for customers to leave; rare and trust-building. **Tags**: #xref #aphorisms  ### [H5] Human connection is DevRel's AI-proof core > [!quote] ID:rw_pending > a people element to this that AI will never replace **Context & use**: - ≈37:10 — DeMars, immediately after "You have to care"; Harper extends it: personality is what companies hire. - The episode's defensibility thesis for DevRel careers amid AI automation. **Tags**: #xref #share  ### 🧠 Permanent Candidates (H4) #### [P1] Internal advocacy needs a build-break-report ritual **Claim** (one sentence, Courtney's voice): 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. **Evidence pointer**: [[#H3]] — DeMars's advocate-hat-off, developer-hat-on workflow (≈10:01-10:46) **Scope & conditions**: Holds for any product with docs and a quickstart; breaks when advocates lack the engineering background to rebuild credibly, or when findings have no routed backlog. **Links** (≥1 with annotation): - [[Developer experience audits]] — because applies-in WordPress quickstart and DevHub reviews - [[DevRel business case]] — because extends the funnel-plus-roadmap justification with an auditable input - [[AI-generated content in DevRel]] — because contrasts on what stays human (judgment from doing) versus automatable output  ### ✏️ Fleeting Queue - [F1] Check whether the reported X/Twitter engagement recovery shows up in courtneyr.dev social referral stats over the next month — https://www.youtube.com/watch?v=cASKKadsefo #fleeting #inbox - [F2] Look up TuxCare SecureChain's vetting model as a comparison point for plugin provenance/FAIR discussions — https://tuxcare.com #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Run a developer-hat docs rebuild on one WordPress quickstart and file every discrepancy — DevRel practice, per DeMars workflow #things - [ ] Compare two weeks of X/Twitter vs LinkedIn engagement on reshared evergreen posts — distribution retest after algorithm change #things  📄 **Full text:** [[Full Document Contents/Articles/Devrelshow Episode 53 - Chris DeMars From TuxCare.md|Devrelshow Episode 53 - Chris DeMars From TuxCare by Frédéric Harper]] ## Highlights - users and we are ambassadors to the product and the organization. So we have to be there for them both internally and externally. And that is what being a ([View Highlight](https://read.readwise.io/read/01kxr9redf650b5qamqtny42vf)) - Note: H2 — ambassadors in both directions: to users AND to the product/organization. Harper notes no guest in 53 episodes had used "ambassador" before. - Tags: atom/literature/h2 - years. You're a developer. You you have to be a developer first to be a developer advocate. So I take the dev ([View Highlight](https://read.readwise.io/read/01kxr9rhkhbe2c1m6qdhmqjq7a)) - Note: The contested credibility-gate claim: developer first, advocate second — backed by his advocate-hat-off demo-and-docs testing workflow. - Tags: atom/literature/h2 - out. But I frame Devril not as a team but as a mission at the end of the day. Yes, on paper ([View Highlight](https://read.readwise.io/read/01kxr9rbwzc2xshs869hn0nre3)) - Note: H1 — DeMars's core framing: DevRel is a mission, not a team ("Devril" is the auto-caption spelling). Org chart on paper, ambassadorship in practice. - Tags: atom/literature/h1 - keep you patched while you figure out your own migration path. So, like I I ([View Highlight](https://read.readwise.io/read/01kxr9rkbve84b640cxew758q3)) - Note: TuxCare's positioning: "a patch while you figure out your patch" — a vendor explicitly planning for customers to leave. - Tags: atom/literature/h3 - going to there's a people element to this that AI will never replace and ([View Highlight](https://read.readwise.io/read/01kxr9rp6yd6r5pbnf2dvpqf7r)) - Note: The episode's defensibility thesis: AI handles brainstorming and scaffolding; the human relationship layer is what companies actually hire DevRel for. - Tags: atom/literature/h3