AI agents can execute more developer work, but people still decide which products to evaluate, learn, trust, and recommend. DevRel work aimed at those decisions depends on identifiable people with a public record of judgement.
The working argument
When agents write the code, developers still choose what to build, what to integrate, what to advocate for inside their teams, and whom to trust. Those choices depend partly on reputation and judgement. As agents handle more mechanical work, DevRel’s influence rests increasingly on whether people trust the humans representing a product.
The dual-audience split leaves these choices with people (see ./the-dual-audience-thesis.md). Agents can carry out more of the work, while humans still decide why to do it, which approach to take, and whom to trust.
What “inspiration” means in practice
When this file says “inspiration,” it means the work of giving a developer a reason to choose to engage with your product. Specifically:
- A reason to evaluate. Why is this product worth two hours of evaluation time?
- A reason to advocate inside their organisation. Why should they put their reputation behind it in an architecture meeting?
- A reason to invest in learning it. Why is this technology worth becoming an expert in?
- A reason to feel something about it. Curiosity, excitement, identification with a community, aesthetic appreciation, intellectual delight.
AI assistants can repeat these reasons from existing material. The original judgement still comes from a person or community willing to attach a name to it.
The channels where inspiration lives in 2026
YouTube
YouTube is a major human-facing DevRel surface in 2026. The format has expanded beyond tutorial videos to include:
- Build-in-public vlogs. Founders or senior engineers narrating decisions over weeks.
- Live coding streams. Real engineers solving real problems, including the failure paths.
- Conference talk recordings. Often the talk reaches more developers post-event than during.
- Sponsored content with trusted educators. Fireship’s Code Report, ThePrimeagen, Theo Browne, and similar channels reach large developer audiences. Sponsorship gives a product access to the trust those educators have already earned.
- Founder-led explainer videos. Patrick Collison or Guillermo Rauch can explain product decisions with the authority of the person who made them.
AI assistants can also retrieve YouTube transcripts, as discussed in ./geo-aeo-for-devrel.md. The video therefore reaches people directly and can become source material for later AI answers.
Conferences and in-person events
In-person conferences remain useful as AI mediates more digital discovery:
- Attendees can ask follow-up questions and watch how speakers handle uncertainty.
- A live demo shows how the product behaves outside a prepared screenshot or edited recording.
- The networking effects compound: a senior engineer who meets your team at re:Invent is more likely to advocate for your product later.
- Conference talks become YouTube content with months-long discovery tails.
The 2024 to 2026 recovery in conference attendance after the pandemic is consistent with this thesis. See ../07-conferences/flagship-conferences.md.
Live streaming (Twitch and YouTube Live)
Live streams let viewers watch an identifiable person work through a problem, including search queries, misreads, and the eventual fix. ThePrimeagen and Tsoding do this on Twitch, and Stripe engineers have used YouTube Live for similar sessions. The visible process and accountable speaker provide evidence that a polished generated demonstration does not.
Founders and senior engineers on X / Bluesky / LinkedIn
The “founder voice” pattern (see ../06-people/founders-as-devrel.md) is useful because the speaker is accountable for the product decisions being discussed. Examples include Patrick Collison on payments architecture, Mitchell Hashimoto on infrastructure tooling, and Guillermo Rauch demonstrating Next.js.
LinkedIn has emerged as a particularly important venue in 2026 for senior-engineer audience (engineering directors, VPs, CTOs): the people who approve technology choices.
Podcasts
Long interviews let listeners hear how a practitioner reasons beyond a prepared launch message. The Changelog, Latent Space, Syntax.fm, Acquired, Lex Fridman Podcast, Practical AI, and Community Pulse all carry product and industry discussions to established audiences.
Discord and named-community spaces
Real-time presence in Discord servers (Vercel, Supabase, Cloudflare, Cursor, Anthropic) maintains community trust. AI assistants can answer the easy questions; the harder questions, the ones with real stakes, still flow through community channels where named, accountable humans respond.
Some AI assistants retrieve Reddit threads heavily. For DevRel teams, the useful work remains substantive participation in communities such as r/programming, r/learnprogramming, r/MachineLearning, r/LocalLLaMA, and r/ExperiencedDevs.
What “inspiration” excludes
Some failure modes that pretend to be inspiration:
- Generic content marketing. “Five best practices for X” articles aren’t inspiration; they’re SEO bait. AI assistants make this content less valuable than ever.
- Unowned AI-generated developer content. It tends towards generic claims and leaves no accountable author when a technical judgement is wrong.
- Case studies with no trade-offs. Developers recognise marketing copy that withholds constraints or failed attempts. Specific limits make the account more useful.
- Generic brand posts on social. A corporate account posting “Our team is excited to share…” gives the reader little reason to care. A named engineer can explain what changed and why.
As mechanically produced material becomes common, identifiable authors and a visible record of judgement become easier to distinguish. DevRel teams can support that by publishing work from founders, engineers, educators, and community members under their own names.
What the inspiration audience trusts
Specific signals that human developers weight heavily in 2026:
- Founders writing honestly. Stripe Press essays, Mitchell Hashimoto on his blog after leaving HashiCorp, individual posts from senior engineers at Anthropic and OpenAI.
- In-public iteration. Supabase Launch Weeks, Vercel’s roadmap thread, Cloudflare’s Developer Week.
- Recognised voices. A recommendation from someone with a relevant public record gives readers a reason to investigate.
- Customer accounts in the customer’s own words. The engineer can explain the constraints, failures, and trade-offs that a vendor case study may omit.
- Conference talks that take risks. A talk that admits failure or pushes a controversial argument gets remembered.
- Working live demos. A successful unedited demo gives the audience evidence that the product works under pressure.
The published record
Readers can inspect what a named person recommended, built, corrected, and defended over time. A prompt can help draft a post, but it cannot supply that history of decisions and public work.
How DevRel teams should staff for inspiration
Teams investing in this work in 2026:
- Hire for voice, presence, and technical ability. An advocate with 50K Bluesky followers and a YouTube channel may inspire more developers than a technically deeper advocate with no public presence.
- Invest in long-form formats. Conference talks, YouTube tutorials, podcasts, in-public series. These compound.
- Pay external creators. Sponsoring trusted YouTubers and podcasters is often more effective than producing more internal content.
- Let the founder be visible. Don’t bottleneck founder content through marketing approval.
- Treat conferences seriously. Speaker placement, side events, customer dinners. The relationships compound.
- Maintain real community presence. Use named people in Discord, on Reddit, and in long-running threads rather than bots or generic accounts.
- Measure with patience. Inspiration is a multi-quarter signal. Don’t pull the plug on a YouTube channel at month three.
Operating both sides
Agents now carry out a meaningful share of developer work, so DevRel teams need accurate machine-readable surfaces. People still decide what to build, adopt, and recommend, so those teams also need credible authors, speakers, educators, and community participants. The staffing and output plan should account for both kinds of work.