samber/developer-relations-skillsチェック済み
SKILL DETAIL
devrel-radar
samber/developer-relations-skills/devrel-radar
Builds a personalised, time-budgeted watch list of developer-relations information sources - DevRel podcasts, newsletters, practice hubs, peer communities, conference calendars, ecosystem data reports and practitioners worth following - plus the routine that keeps it verified and fresh. Use whenever a developer advocate, community manager, DevRel lead or OSS maintainer asks for a DevRel radar, how to stay current on developer relations, which DevRel podcasts, newsletters or Slack communities deserve their time, which developer conferences to attend or speak at, who to follow in DevRel, or to refresh a radar built earlier - even if they only say they feel out of the loop. Not for tracking a rival vendor - use samber/developer-relations-skills@devrel-competitor-analysis.
インストール · 422出典を見る
Installation
npx skills add https://github.com/samber/developer-relations-skills --skill devrel-radar
スキルファイル
SKILL.md
最終同期 · 2026/10/23
evals/evals.json›
{
"skill_name": "devrel-radar",
"evals": [
{
"id": 1,
"prompt": "I'm the second DevRel hire at Kestrel Data - we sell a streaming SQL engine to backend teams, bottom-up, self-serve signup, credit card at the bottom tier. I own advocacy and developer marketing, and I just picked up community when our last community manager quit. I can give this 90 minutes a week, no more. I cycle 35 minutes each way to the office and I listen to things on the ride. I read fine. I never watch video, ever. Give me what I should be following and tell me what to open first.",
"expected_output": "A time-budgeted watch list ordered by value per attention-minute, with commute audio halved, conferences kept off the weekly line, roughly 10% of the budget reserved for a peer community, all three owned pillars covered, and video deleted and named as dropped.",
"files": [],
"expectations": [
"Asks the interview questions it still lacks - which developer ecosystem the user works in, whether they are catching up before a specific moment or building a standing habit, and whether they need to speak, sponsor or organise events this year - before finalising the list, one question at a time rather than as a single block.",
"Orders the list by value returned per attention-minute and states that ordering explicitly in the output rather than leaving it implied by row order.",
"Does not order the list by cheapness, by subscriber count, by follower count, or by audience size.",
"Places an annual ecosystem survey or community-health data report at or near the top of the efficiency ordering, justified as the citable number budget and headcount conversations run on.",
"Halves the attention cost of any podcast assigned to the 35-minute cycle commute, and says the halving is because that time is already spent rather than attention the user has to find.",
"Does not amortise a multi-day conference across 52 weeks, and does not present a conference as a small recurring weekly cost.",
"Spends roughly 90% of the 90-minute budget and reserves roughly the last 10% for one peer community, stating that communities are where new sources surface.",
"Carries at least one verified-active source for each of advocacy, developer marketing and community.",
"Includes at least one source about the DevRel practice itself, not only about streaming data or the user's own technology.",
"Attaches a what-they're-selling flag to every entry, drawn from a specific category such as agency, tool vendor, course or community, conference, platform-official, foundation, or independent media.",
"Attaches a status and a date to every entry.",
"Contains no video entry anywhere in the deliverable, including the bench.",
"Names video in an explicit Dropped line together with the constraint that removed it, rather than ranking video entries last."
]
},
{
"id": 2,
"prompt": "Radar for me please. I'm a community manager at Thornbury Analytics - data-observability SaaS, enterprise deals, everything goes through a sales team and a procurement review. Constraints you should know up front: our IT blocks any Slack workspace we don't own, there is zero budget for paid communities or courses this year, travel is frozen until at least next summer, and I will not pay for a newsletter subscription out of my own pocket. 60 minutes a week. I read and I listen. I own community and enablement.",
"expected_output": "A 60-minute list where every constraint-ruled-out source is deleted outright and named in a Dropped line, the bench holds only budget-excluded sources, and an ungated community route replaces the blocked Slack option.",
"files": [],
"expectations": [
"Removes every Slack-based community outright from the deliverable rather than listing it lower down, marking it optional, or noting it as something to revisit.",
"Removes paywalled newsletters and paid communities or courses outright from the deliverable.",
"Removes travel-dependent conferences outright for the frozen period rather than ranking them low.",
"Includes a Dropped line naming each removed source together with the specific constraint that removed it.",
"Places no ruled-out source at the bottom of the list, in a nice-to-have section, or in the bench.",
"Distinguishes the bench from the dropped sources, defining the bench as verified sources the budget merely could not fit.",
"Names 2-3 bench substitutes.",
"Offers an ungated, non-Slack peer community route - such as a public mailing list, an open community calendar, or a public forum - instead of leaving the community pillar uncovered.",
"Carries at least one verified-active source for community and at least one for enablement.",
"Does not pad the list with sources whose only justification is advocacy or developer marketing, pillars this user does not own.",
"Notes that a top-down enterprise platform segment adds the ecosystem's own foundation and standards-body sources, without changing which pillars must be covered.",
"Attaches a what-they're-selling flag, a status and a date to every entry."
]
},
{
"id": 3,
"prompt": "I inherited a list of DevRel sources from the person who had this job before me and I want to know what's still worth anything. Here's what I checked in a browser this morning: devrelx.com loads fine but the page is about a brewing company. karlhughes.com shows a 'this domain is for sale' parking page. devrelfoundation.org gives me a DNS error. developerweek.com returns a 403. And the Scaling DevTools podcast site returns a 403 too. Tell me what to keep and what to bin.",
"expected_output": "A per-URL verdict that separates evidence about a URL from evidence about the entity behind it: the resold domain hard-removed, the parked personal domain marked unverified rather than inactive, the NXDOMAIN treated as evidence about the guess, and both 403s classified unverified with the feed named as the datable surface.",
"files": [],
"expectations": [
"Classifies devrelx.com as dead or resold and instructs the user never to link it, because the destination is an unrelated business even though the URL resolves.",
"States explicitly that a resolving URL is not evidence the entity behind it is intact, and that the destination's content must be confirmed rather than only that the URL loads.",
"Classifies Karl Hughes as unverified rather than inactive, on the ground that a parked personal domain is evidence about the domain, not about the person.",
"Points at the person's company surface, draft.dev, as where to track him instead of the parked personal domain.",
"Treats the devrelfoundation.org DNS failure as evidence about the guessed domain, not about the organisation.",
"Identifies the Developer Relations Foundation as alive at dev-rel.org and hosted by the Linux Foundation.",
"Describes finding an organisation through its code-host organisation page - its declared website field, its repositories sorted by last push, and its repository descriptions - instead of guessing another domain.",
"Classifies the DeveloperWeek 403 as unverified and explicitly not dead, recording the bot-block as the reason.",
"Classifies the Scaling DevTools 403 as unverified for the homepage while naming the podcast feed as the surface that does carry dates.",
"States that podcast feeds beat marketing homepages for establishing dates.",
"Reports none of the five as verified-active without a dated item actually observed.",
"Assigns each of the five an explicit verdict from the active / stale / dead / unverified classification rather than a narrative judgement.",
"Records a reason alongside every unverified verdict."
]
},
{
"id": 4,
"prompt": "We want to sponsor DevRelCon this year - I've got about $15k plus a booth budget. I'll email Hoopy to ask about packages. Can you confirm the dates for me, and tell me what else on the DevRel event calendar is worth the spend? I'm head of DevRel at Ambervale, we do CI/CD tooling, 30 people.",
"expected_output": "A correction of the organiser (Hoopy wound down, Major League Hacking now runs DevRelCon), confirmed dates, an owner check applied to every other recommended event, and conferences costed as cleared days rather than weekly minutes.",
"files": [],
"expectations": [
"Corrects the organiser: the agency Hoopy wound down in 2026 and handed DevRelCon to Major League Hacking.",
"States that the sponsorship enquiry should go to Major League Hacking rather than Hoopy.",
"Confirms the DevRelCon New York edition as 22-23 July 2026.",
"Gives the event's approximate scale as around 300 attendees rather than implying a mass-market audience.",
"States that a freshness check passing on a date says nothing about the organiser, and that date and owner must both be checked.",
"Verifies or flags the organiser for every other event it recommends, not only the dates.",
"Flags at least one event whose page does not render a year - such as a KubeCon North America listing showing 9-12 November with no year - and tells the user to confirm before booking.",
"Distinguishes what the field's own practice conference buys from what a large general developer conference buys, rather than treating them as interchangeable sponsorship targets.",
"Does not invent a sponsorship price, package tier, or prospectus figure it has not observed.",
"States that the event calendar needs refreshing twice a year rather than quarterly, because CFP deadlines land months before the event itself.",
"Keeps conferences off the weekly efficiency line, describing their cost as cleared days plus travel rather than as minutes per week.",
"States that because this user is sponsoring, the event calendar becomes core to the radar rather than an optional extra."
]
},
{
"id": 5,
"prompt": "Honest question - is there anything in developer relations that isn't somebody's funnel? Every podcast host has a consultancy, every newsletter is an agency's lead magnet, and every 'research report' comes from a tool vendor who wants me to buy their thing. I'm a developer advocate at Lorrick, we ship embedded and IoT SDKs. 75 minutes a week, I read and I listen. Give me something I can actually trust.",
"expected_output": "The Developer Relations Foundation named first as the field's only vendor-neutral practice body with the reason it is the exception, plus a full list that discloses each incentive instead of filtering conflicted sources out.",
"files": [],
"expectations": [
"Leads with the Developer Relations Foundation at dev-rel.org and identifies it as the field's only vendor-neutral practice body.",
"States that the Foundation is hosted by the Linux Foundation, and explains why that makes it the exception rather than one neutral option among several.",
"Refuses to filter conflicted sources out of the list, and explains that doing so would empty it because almost every strong voice in this field runs an agency, a startup or a paid community.",
"Attaches a specific what-they're-selling category to every entry - agency, tool vendor, course or community, conference, platform-official, foundation, or independent media - rather than a single blanket disclaimer.",
"Frames the flag as disclosure so the user can weigh advice, explicitly not as grounds for disqualification.",
"Includes at least one foundation or platform-official source beyond the Foundation itself, such as an open community-health metrics project or a code host's maintainer guides.",
"Does not present a vendor's content arm or a VC firm's podcast network as neutral.",
"Flags at least one source whose angle changed after an acquisition, noting that cadence can survive an acquisition while the DevRel angle does not.",
"Keeps at least one commercially conflicted source in the final list with its incentive disclosed, rather than removing it.",
"States that embedded or IoT ecosystem sources sit next to the practice sources rather than replacing them.",
"Totals estimated weekly minutes against the 75-minute budget.",
"Orders the entries by value per attention-minute and says so in the output."
]
},
{
"id": 6,
"prompt": "Three things on my list have no dates anywhere on the site and it's driving me mad: diataxis.fr, GitHub's opensource.guide, and the guides section of developerrelations.com. Should I assume they're abandoned and drop them? And how many minutes a week should I budget for each? I own docs and community at Pellier, an open-source workflow engine.",
"expected_output": "All three treated as evergreen reference works: no staleness verdict, judged on maintenance signals, placed outside the weekly budget, and given no per-week minutes figure.",
"files": [],
"expectations": [
"Refuses to assign a staleness verdict to any of the three, on the ground that a reference work has no cadence to be stale against.",
"Labels each of the three evergreen and undated, or an equivalent explicit classification, rather than stale or dead.",
"Judges each on maintenance signals instead - a live event listing, a current copyright, an active repository.",
"Cites at least one concrete maintenance signal for developerrelations.com, such as its current copyright range or the upcoming DevRelCon edition it lists.",
"Places all three outside the weekly time budget rather than inside it.",
"Declines to give any of the three a minutes-per-week figure, and explains that a per-week ratio on a one-time read is false precision.",
"Describes them as a one-time read to revisit when scoping work, not as a recurring feed.",
"Maps Diataxis to the enablement pillar and the code host's maintainer guides to the community pillar.",
"Identifies developerrelations.com as the field's practice canon and notes that it survived the wind-down of the agency that founded it.",
"Does not invent a publication date or last-updated date for any of the three.",
"Still supplies dated, verified feed sources covering the docs and community pillars alongside the three reference works."
]
},
{
"id": 7,
"prompt": "I don't read. Genuinely - I retain nothing from text. I watch everything on YouTube. Build me a DevRel channel list ranked by subscriber count so I know who the biggest ones are, and tell me how many minutes a week each costs. I'm a developer advocate at Verrick, we do a GraphQL gateway, and I have about 2 hours a week.",
"expected_output": "A refusal to rank by subscriber count or to assert unobservable channel figures, a fetchable conference-talk archive offered as the substitute, any named channel labelled as unobserved with its corroborating surface, and the cost of a video-only radar stated plainly.",
"files": [],
"expectations": [
"Refuses to rank by subscriber count, and explains that social rating measures reach in an adjacent audience rather than standing in this one.",
"States that subscriber counts and upload dates on video platforms are not observable to an automated check, because the platform answers with a consent wall or redirect.",
"Asserts no subscriber count for any channel.",
"Does not invent or list a plausible-sounding channel name to fill the gap.",
"Recommends a fetchable conference-talk archive as the substitute for an unverifiable channel, naming the DevRelCon talk archive published on developerrelations.com as an example.",
"Labels any channel it does name as channel itself unobserved, or an equivalent, and names the companion surface that corroborates it - the creator's own site or a conference programme.",
"States that video sits last on the efficiency ordering and last on the value ordering.",
"Tells the user plainly that a video-only radar is the weakest configuration available and says what it costs them.",
"Costs a conference-talk video as tens of minutes, an order of magnitude rather than a precise figure.",
"Does not quietly substitute text sources the user said they will not consume without naming the trade-off.",
"Attaches a what-they're-selling flag, a status and a date to every entry it does deliver.",
"Offers at least one live or community surface - a conference, a meetup, a recurring community call - as a non-text, non-channel way to cover the gap."
]
},
{
"id": 8,
"prompt": "I start as a developer advocate at Hollick Systems in three weeks. It's my first DevRel job - I was a platform engineer before that. I've got about 2 hours a week I can carve out and I want to use the next month to actually get up to speed before day one. Fully remote, so no commute, and no travel budget until the next fiscal year. I'll own advocacy and enablement. What's my list?",
"expected_output": "A list that promotes long-form against the efficiency ordering, names the promotion conditions (new to DevRel, catching up), states what the ratio starves, and does not halve audio for a user with no commute.",
"files": [],
"expectations": [
"Promotes long-form sources - podcasts, conference talks, a peer community - into the list rather than letting the efficiency ordering exclude them.",
"Names the specific conditions that trigger the promotion here: the user is new to DevRel and is catching up before a moment rather than building a standing habit.",
"States explicitly what the efficiency ordering starves - that a budget filled strictly top-down by ratio buys no podcasts, no talks, no conferences and no community.",
"Explains that long-form is where a practitioner's reasoning is visible, while text mostly reports the conclusion.",
"Includes at least one podcast about the DevRel practice itself rather than only about a technology.",
"Reserves a peer community slot and describes it as a standing floor rather than a reward for winning the ratio.",
"Does not halve any audio cost, since a fully remote user with no commute has no already-spent time for it to ride on.",
"Carries at least one verified-active source for advocacy and at least one for enablement.",
"Distinguishes this catching-up configuration from the standing weekly habit the user will need afterwards, and says what changes between them.",
"States the ordering used and totals estimated minutes against the 2-hour budget.",
"Does not carry a conference as a weekly line item given there is no travel budget, and drops or benches it explicitly rather than ranking it low.",
"Does not present the field's evergreen reference works as a recurring weekly cost.",
"Attaches a what-they're-selling flag, a status and a date to every entry."
]
},
{
"id": 9,
"prompt": "Quarterly check-in on the radar you put together for me. What's changed since last time: I picked up the developer marketing pillar on top of community, my company approved a EUR 4k conference budget, and honestly I didn't open either of the two newsletters all quarter - I did read or listen to everything else. Also that application-gated Slack I couldn't get into, a colleague on my team is in it now. Still 60 minutes a week. What changes?",
"expected_output": "A refresh pass that re-asks pillars and restores coverage for the new one, re-resolves every URL, drops the unread newsletters, re-ranks on the conference budget and names which fact moved which source, and treats the colleague as someone to ask rather than a reason to join.",
"files": [],
"expectations": [
"Re-asks which pillars the user owns, and treats the newly acquired developer marketing pillar as voiding the coverage guarantee until a source covers it.",
"Adds at least one verified-active developer marketing source to restore pillar coverage.",
"Re-resolves every URL on the existing list, including the ones that worked last time, to catch renames, acquisitions and resold domains.",
"Re-runs the freshness and ownership check: downgrades newly stale entries, removes dead ones, and retries previously unverified ones.",
"Drops the two unread newsletters, on the stated ground that an unread source costs attention anyway.",
"Re-ranks against the new conference budget and states that a budget turns an event from a personal expense into a cleared slot.",
"Names which new fact moved which source, rather than presenting a silently reordered list.",
"Treats the colleague inside the gated community as someone to ask, rather than as a reason to join the community.",
"Does not re-offer any source previously deleted for a constraint unless the user has said that constraint lifted.",
"Refreshes the event calendar on a twice-yearly rather than quarterly cadence, because CFP deadlines land months before the event.",
"Asks the peer community and the newest additions for one candidate discovery each, and verifies it before promoting it to the bench or the list.",
"Checks the consumption bar - that the user consumed at least two thirds of the entries - and reports the result against it.",
"Re-totals estimated weekly minutes against the 60-minute budget and trims any overflow."
]
},
{
"id": 10,
"prompt": "Heads up: this environment has no network access at all, you can't fetch or open anything. I still want the radar. Developer advocate at Sundermere, we make a vector database sold bottom-up to application engineers. I own advocacy and community, 45 minutes a week, text and audio, absolutely no video. Can you still do it?",
"expected_output": "The list delivered from recorded entries with an explicit statement that nothing could be re-verified, the four-step manual check handed to the user with its thresholds, the snapshot-age warning, and no invented or freshly-claimed verification.",
"files": [],
"expectations": [
"Delivers the list rather than refusing, drawing on its bundled source entries with each one's recorded status and date.",
"States clearly and prominently that it could not re-verify anything in this environment.",
"Carries each entry's previously recorded status and date rather than presenting any of them as freshly confirmed.",
"Hands the user the manual check as explicit steps: open each URL, find the newest dated item, confirm the owner, apply the classifications.",
"Gives the thresholds to apply: a dated item within roughly three months is active, and a newest dated item older than roughly six months is stale.",
"States that the three- and six-month windows are a self-set baseline rather than an industry standard, and should be widened for annual surveys and tightened for a daily news site.",
"Flags the age of the source snapshot it is working from and warns that a snapshot older than roughly six months needs re-verification before being relied on.",
"Labels no entry verified-active on the strength of a remembered date.",
"Invents no source to fill a pillar gap.",
"Covers advocacy and community with at least one source each.",
"Excludes video entirely and names the deletion with the constraint that caused it.",
"Opens the artifact by saying what it is not - a reading list verified on one date, not a monitoring service that alerts the user when a source dies."
]
},
{
"id": 11,
"prompt": "Keep this tight - I only want cloud-native sources. I do DevRel for Skaldis, a Kubernetes storage operator, and everything I read should be about Kubernetes, CNCF, eBPF, that world. I don't need generic career fluff. 90 minutes a week, I own advocacy and community, and I'm submitting talks this year.",
"expected_output": "A refusal to deliver an ecosystem-only list, practice sources placed next to the ecosystem ones, the event line turned on with one CFP target and one attend-or-sponsor candidate, and long-form promoted because speaking makes conferences the work.",
"files": [],
"expectations": [
"Declines to deliver an ecosystem-only list and explains why: following only your own technology's sources leaves the practice itself unlearned.",
"States that ecosystem sources sit next to practice sources, never instead of them.",
"Includes at least one source about the DevRel practice itself despite the user's instruction.",
"Frames those practice sources as craft rather than career content, distinguishing them from what the user dismissed.",
"Adds the cloud-native ecosystem's own foundation and conference sources for the platform and standards layer.",
"Turns the event calendar from optional into core because the user is submitting talks, and gives one CFP target with a confirmed date and a confirmed organiser.",
"Gives one attend-or-sponsor candidate alongside the CFP target, also with a confirmed date and organiser.",
"Promotes long-form on the stated ground that submitting talks makes conferences the work rather than a reading cost.",
"Does not amortise a conference into a weekly minutes figure.",
"Carries at least one verified-active source for advocacy and at least one for community.",
"States the ordering used and totals estimated weekly minutes against the 90-minute budget.",
"Attaches a what-they're-selling flag, a status and a date to every entry."
]
},
{
"id": 12,
"prompt": "I'm writing the slide that saves my team's headcount next week. I need hard numbers: how many developers are out there, what share of them use AI coding tools, and what a normal DevRel team size and budget looks like. Just give me the stats and I'll drop them straight in. I'm DevRel lead at Ferrocast, about 120 developers hit our API weekly.",
"expected_output": "Named data sources each carried with edition and date rather than bare statistics, the annual data family treated as first-class for a budget defence, the metrics index described as definitions rather than benchmarks, and no fabricated figures.",
"files": [],
"expectations": [
"Refuses to supply bare statistics, and instead names the sources with each one's edition and date.",
"States explicitly that a bare statistic ages invisibly and gets repeated in a leadership deck.",
"Names GitHub Octoverse as the annual open-source and language-ecosystem source, with the 2025 edition published 28 October 2025.",
"Names the JetBrains State of Developer Ecosystem with its edition and field details - 24,534 respondents, fielded April to June 2025.",
"Names the Stack Overflow Developer Survey and flags that its edition's publication date was not confirmed.",
"Names SlashData for developer population sizing and ecosystem segment sizing.",
"Names a community-profession benchmark source for team size and budget figures, specifically the CMX Community Industry Report and its 2026 seventh edition.",
"Describes the Developer Relations Foundation Metrics Index as an early-stage definitions reference rather than a benchmark dataset to quote numbers from.",
"Treats the annual data family as a first-class source category precisely because this user must justify budget or headcount upward, not as background reading.",
"Costs each annual report as one concentrated read a year rather than as a weekly line item.",
"Places the annual data report at the top of the efficiency ordering while stating it is not the most valuable source type.",
"Fabricates no specific percentage, developer population figure, median team size or budget number."
]
},
{
"id": 13,
"prompt": "Give me the top 10 people in DevRel ranked by follower count, with their Twitter and LinkedIn handles - I want to follow the biggest voices in the space. I'm community lead at Draymoor, we sell an API gateway, and I own community and advocacy.",
"expected_output": "A refusal to rank by follower count, ranking by cross-surface recurrence instead, each person tied to a fetchable verifying surface with an incentive disclosure, filtered to the user's two pillars.",
"files": [],
"expectations": [
"Refuses to rank by follower count and explains that social rating measures reach in an adjacent audience rather than standing in this one.",
"States that follower and subscriber counts are largely unobservable in this field anyway.",
"Ranks by cross-surface recurrence instead - the same person appearing as podcast host, conference speaker and practice-hub author.",
"Gives each person a fetchable verifying surface - a podcast feed or episode page, a company site, a talk listing, a foundation project page - rather than a social profile.",
"States that short-post and professional social networks block automated checking, so nobody can be verified through a social profile.",
"Labels any handle it does record as stated on the page where it appeared, never independently verified.",
"Attaches a what-they're-selling disclosure to every person listed.",
"Frames that disclosure as weighing advice rather than disqualifying anyone, noting that nearly everyone in this field sells something.",
"Filters the people list to the community and advocacy pillars the user owns rather than returning an undifferentiated roster.",
"Marks anyone whose only surface is stale as stale with its approximate age, rather than presenting them as current.",
"Does not link a personal domain without confirming that the page's content is actually about developer relations.",
"States that a role change is a source change, because the expertise survives the move while the incentive shifts."
]
},
{
"id": 14,
"prompt": "We make a coding-education platform for teenagers in Brazil - free for schools, paid subscription for families. I'm the only DevRel-ish person here and I'm mostly self-taught at it. I'd like sources in Portuguese if any exist, plus whatever the profession itself reads. 60 minutes a week, I own community and enablement, and I speak at teacher and education conferences a few times a year.",
"expected_output": "A list that keeps the four pillars but swaps the reach and community sources for the education-facing segment, names the thin coverage of that segment honestly, gives the Portuguese-language source with its real stale status, and invents nothing to pad the regional section.",
"files": [],
"expectations": [
"States that the field's source population is predominantly B2B devtool sources, rather than implying the list is segment-neutral.",
"Keeps the four pillars unchanged for a consumer and education-facing product, and says so explicitly.",
"States that reach and community sources differ for this segment - student and hackathon networks, creator platforms - and names at least one such source.",
"Warns that the consumer and education-facing segment is covered thinly compared with the B2B population, and that the user should treat that as a real gap.",
"Does not pad the list with extra entries to hide that gap.",
"Names at least one Portuguese-language Brazilian DevRel source, specifically the Abacate DevRel work by Pachi Parra, with its status.",
"Marks that Portuguese-language source as stale with its approximate age rather than presenting it as current.",
"Invents no additional Portuguese-language DevRel podcast, newsletter or community to fill out the regional section.",
"Includes English-language practice sources alongside the regional ones rather than substituting one for the other.",
"Turns the event line on because the user speaks, giving one CFP target and one attend-or-sponsor candidate, each with a confirmed date and a confirmed organiser.",
"Carries at least one verified-active source for community and at least one for enablement.",
"Totals estimated weekly minutes against the 60-minute budget and states the ordering used."
]
},
{
"id": 15,
"prompt": "Realistically I have 25 minutes a week. That's it. I'm a technical writer at Ostley - payments API - and after a layoff round I got handed the developer community as well. Text only, I can't listen to anything at my desk and I don't commute. Tell me the minimum viable version. Also, someone told me to subscribe to DevRel Weekly - is that still a thing?",
"expected_output": "A compressor-led 25-minute list, audio deleted and named, an accurate answer on DevRel Weekly's format change, a 2-3 entry bench, and an ordering by efficiency rather than by cheapness.",
"files": [],
"expectations": [
"Adds a budget compressor first, because the budget sits under roughly 60 minutes a week.",
"Defines the compressor as one daily developer-news site or weekly roundup that substitutes for following several vendor blogs individually, and names a specific one.",
"Answers the DevRel Weekly question directly: the newsletter changed format and should be listed as sporadic or occasional, not weekly.",
"Attributes that change to the curator's own announced wind-down of the weekly cadence, explicitly not to the site being dead or to an infrastructure failure.",
"Deletes every audio source outright and names the deletion with the constraint that caused it.",
"Stops when the 25-minute budget is spent, even though strong sources remain unlisted.",
"Names 2-3 bench substitutes and defines the bench as verified sources the budget could not fit.",
"Carries at least one verified-active source for enablement and at least one for community.",
"Places the field's evergreen docs framework or maintainer guides outside the weekly budget as a one-time read, not as a weekly line item.",
"States the efficiency ordering explicitly rather than implying it by row order.",
"Does not rank a five-minute newsletter first merely because it is the cheapest option available.",
"Totals the estimated weekly minutes against the 25-minute budget.",
"Attaches a what-they're-selling flag, a status and a date to every entry."
]
}
],
"trigger_queries": [
{ "query": "Build me a DevRel radar - solo advocate at an API company, about an hour a week.", "should_trigger": true },
{ "query": "Which DevRel podcasts are actually still active?", "should_trigger": true },
{ "query": "I feel completely out of the loop on developer relations. Where do I even start?", "should_trigger": true },
{ "query": "what should i be reading to stay current in devrel", "should_trigger": true },
{ "query": "Who should I be following in developer relations, and what are they selling?", "should_trigger": true },
{ "query": "Refresh the DevRel radar you built me last quarter.", "should_trigger": true },
{ "query": "I run docs and community for a Kubernetes tool. What should I read, and which conferences should I submit to?", "should_trigger": true },
{ "query": "Curate a weekly reading list for a developer advocate with 45 minutes a week.", "should_trigger": true },
{ "query": "Are there any good newsletters for developer marketing?", "should_trigger": true },
{ "query": "I just got my first developer advocate job and I have no idea what the field reads.", "should_trigger": true },
{ "query": "Which Slack or Discord communities are worth joining if I do community for a devtool?", "should_trigger": true },
{ "query": "Give me a list of DevRel conferences worth attending over the next year.", "should_trigger": true },
{ "query": "My manager wants me to justify our DevRel budget. Which annual surveys should I be citing?", "should_trigger": true },
{ "query": "Is DevRel Weekly still going?", "should_trigger": true },
{ "query": "What's the trade press for developer relations, if there is any?", "should_trigger": true },
{ "query": "I have a 40 minute commute each way. What should I listen to that makes me better at my job as an advocate?", "should_trigger": true },
{ "query": "Set me up with a sustainable habit for keeping up with my field - I'm a developer advocate.", "should_trigger": true },
{ "query": "Which DevRel information sources are dead now?", "should_trigger": true },
{ "query": "help me build a watch list of sources for developer relations", "should_trigger": true },
{ "query": "I'm moving from backend engineering into developer advocacy. What do I need to start following?", "should_trigger": true },
{ "query": "Please assemble a prioritised list of developer-relations information sources fitting a two-hour weekly budget.", "should_trigger": true },
{ "query": "Which of these are still publishing? devrelweekly.com, devrelx.com, console.dev", "should_trigger": true },
{ "query": "Is devrelx.com legit? The link works but it takes me somewhere strange.", "should_trigger": true },
{ "query": "Who actually runs DevRelCon these days?", "should_trigger": true },
{ "query": "I have almost no time. What is the single highest-value thing to read each week in DevRel?", "should_trigger": true },
{ "query": "I keep hearing about a DevRel foundation but I can't find their website anywhere.", "should_trigger": true },
{ "query": "give me podcasts about developer experience and devtool growth", "should_trigger": true },
{ "query": "I want to stop doomscrolling and actually learn my profession. I do community for a dev tool.", "should_trigger": true },
{ "query": "What should a technical writer who owns developer docs be reading every week?", "should_trigger": true },
{ "query": "Which developer relations sources cover the enablement pillar?", "should_trigger": true },
{ "query": "Build a quarterly refresh routine for my professional reading.", "should_trigger": true },
{ "query": "I only have time for one podcast. Which one?", "should_trigger": true },
{ "query": "Can you check whether the sources on my DevRel reading list are still alive?", "should_trigger": true },
{ "query": "Recommend French-language resources on developer relations.", "should_trigger": true },
{ "query": "Are there Japanese DevRel communities I could join?", "should_trigger": true },
{ "query": "What do people in developer relations actually read?", "should_trigger": true },
{ "query": "I'm a solo OSS maintainer trying to do DevRel. What should I follow without it eating my week?", "should_trigger": true },
{ "query": "Give me a source list for developer marketing, with who's behind each one.", "should_trigger": true },
{ "query": "Everything in DevRel seems to be consultants selling something. Is there anything neutral?", "should_trigger": true },
{ "query": "Put together my information diet for developer relations.", "should_trigger": true },
{ "query": "Which conferences should I submit a talk to as a developer advocate this year, and when are the CFPs?", "should_trigger": true },
{ "query": "What are the annual developer ecosystem surveys I should know about?", "should_trigger": true },
{ "query": "I want an OPML file of DevRel feeds I can import into my reader.", "should_trigger": true },
{ "query": "how do i stay up to date on devrel without it eating my whole week", "should_trigger": true },
{ "query": "Which DevRel blogs are worth a weekly skim?", "should_trigger": true },
{ "query": "I've been out of the field for two years. What changed, and what should I read to catch up?", "should_trigger": true },
{ "query": "Find me communities where DevRel people actually answer each other's questions.", "should_trigger": true },
{ "query": "Rank these DevRel sources by what I should read first with an hour a week.", "should_trigger": true },
{ "query": "What's worth following if I do developer advocacy in the AI tooling space?", "should_trigger": true },
{ "query": "Give me a short list of people whose writing on developer relations is worth my time.", "should_trigger": true },
{ "query": "Trim my reading list - it has thirty things on it and I read none of them.", "should_trigger": true },
{ "query": "Which sources should a DevRel lead read, versus an individual advocate?", "should_trigger": true },
{ "query": "I need to know what's happening across the developer tools world every week.", "should_trigger": true },
{ "query": "Is Jono Bacon still writing?", "should_trigger": true },
{ "query": "Are there any vendor-neutral developer relations resources?", "should_trigger": true },
{ "query": "Check the freshness of the DevRel things I'm subscribed to.", "should_trigger": true },
{ "query": "I want to sponsor a developer relations conference. Which ones exist, and who organises them?", "should_trigger": true },
{ "query": "put together a reading plan for someone new to community management in open source", "should_trigger": true },
{ "query": "Which podcasts cover open source business models and maintainer economics?", "should_trigger": true },
{ "query": "What's the best way to keep discovering new DevRel sources over time instead of reading the same five things?", "should_trigger": true },
{ "query": "I own advocacy and community at a Series A devtool. What's my weekly input supposed to be?", "should_trigger": true },
{ "query": "Which DevRel sources are free and which are paywalled?", "should_trigger": true },
{ "query": "Give me the practice canon for developer relations - the reference works, not the news.", "should_trigger": true },
{ "query": "How often should I re-check my professional source list?", "should_trigger": true },
{ "query": "My DevRel reading list is a year old. Is any of it still valid?", "should_trigger": true },
{ "query": "What do I read to get good at developer relations, not just informed about it?", "should_trigger": true },
{ "query": "Suggest sources for open definitions of community health metrics.", "should_trigger": true },
{ "query": "Which regional DevRel communities exist outside the US and UK?", "should_trigger": true },
{ "query": "I want to hear practitioners reason through hard calls, not just read headlines.", "should_trigger": true },
{ "query": "Which DevRel sources cover the developer marketing pillar specifically?", "should_trigger": true },
{ "query": "Assemble an annual calendar of DevRel events and their CFP windows.", "should_trigger": true },
{ "query": "Who are the people to follow for technical content strategy in developer products?", "should_trigger": true },
{ "query": "I distrust anything written by a tool vendor. Where does that leave me in this profession?", "should_trigger": true },
{ "query": "Give me a 30-minute-a-week plan to stay current as a DevRel engineer.", "should_trigger": true },
{ "query": "What are the Brazilian or Portuguese-language DevRel resources?", "should_trigger": true },
{ "query": "I need sources for both my ecosystem and the DevRel practice itself.", "should_trigger": true },
{ "query": "build my devrel information sources list", "should_trigger": true },
{ "query": "Is there a podcast about the DevRel practice itself rather than about a technology?", "should_trigger": true },
{ "query": "Which DevRel sources changed hands or got acquired recently?", "should_trigger": true },
{ "query": "What should I add to what I follow now that I own the docs pillar too?", "should_trigger": true },
{ "query": "I'd like a verified list of DevRel resources with a date on each one.", "should_trigger": true },
{ "query": "Point me at communities, podcasts and newsletters for developer relations, grouped by type.", "should_trigger": true },
{ "query": "Give me something to listen to at the gym that makes me better at developer advocacy.", "should_trigger": true },
{ "query": "Track what our main competitor's DevRel team is publishing and where they're beating us.", "should_trigger": false },
{ "query": "Build a technology radar for our engineering org - adopt, trial, assess, hold.", "should_trigger": false },
{ "query": "How do I get hired as a developer advocate? Here's my resume, tear it apart.", "should_trigger": false },
{ "query": "Write a job description for a senior developer advocate.", "should_trigger": false },
{ "query": "Help me write a conference talk proposal for KubeCon.", "should_trigger": false },
{ "query": "Should we sponsor this conference at the gold tier or just buy a booth?", "should_trigger": false },
{ "query": "Plan a monthly developer meetup series in Berlin.", "should_trigger": false },
{ "query": "Plan our DevRel content calendar for Q3.", "should_trigger": false },
{ "query": "Which DevRel metrics should we report to the board?", "should_trigger": false },
{ "query": "Set up dashboards for our developer funnel analytics.", "should_trigger": false },
{ "query": "Find the keywords developers search for around our API.", "should_trigger": false },
{ "query": "I'm going on a podcast next week as a guest. Prep me.", "should_trigger": false },
{ "query": "We're launching a Discord for our users. How do we start it properly?", "should_trigger": false },
{ "query": "Our community has gone quiet. How do I measure whether it's actually healthy?", "should_trigger": false },
{ "query": "Write a code of conduct and moderation policy for our forum.", "should_trigger": false },
{ "query": "Design a champions program for our most active users.", "should_trigger": false },
{ "query": "Pitch our launch to tech journalists.", "should_trigger": false },
{ "query": "Design a certification and training path for our platform.", "should_trigger": false },
{ "query": "Write an engineering blog post about our new query planner.", "should_trigger": false },
{ "query": "We're open-sourcing our library next month. Plan the launch.", "should_trigger": false },
{ "query": "Rewrite our README so it actually converts visitors into users.", "should_trigger": false },
{ "query": "Turn these 60 commits into release notes.", "should_trigger": false },
{ "query": "Segment our developer users into personas.", "should_trigger": false },
{ "query": "Write our DevRel strategy for next year.", "should_trigger": false },
{ "query": "Should DevRel report into marketing or into product?", "should_trigger": false },
{ "query": "Split our $400k DevRel budget across programs.", "should_trigger": false },
{ "query": "Map the developer journey from first search to first successful deploy.", "should_trigger": false },
{ "query": "Script a five-minute product video aimed at developers.", "should_trigger": false },
{ "query": "Outline a 25-minute conference talk on eBPF.", "should_trigger": false },
{ "query": "Should I share our MRR publicly as a bootstrapped maintainer?", "should_trigger": false },
{ "query": "Our docs don't rank on Google at all. Fix the SEO.", "should_trigger": false },
{ "query": "Improve my GitHub profile README.", "should_trigger": false },
{ "query": "Audit the structure and information architecture of our documentation site.", "should_trigger": false },
{ "query": "Write a tutorial that teaches our SDK from scratch.", "should_trigger": false },
{ "query": "Our quickstart takes 40 minutes. Get it down to five.", "should_trigger": false },
{ "query": "Set up governance for our open-source project.", "should_trigger": false },
{ "query": "We have 400 stale issues. Design a triage process.", "should_trigger": false },
{ "query": "Should our devtool be priced usage-based or per seat?", "should_trigger": false },
{ "query": "Should we take this protocol to a standards body?", "should_trigger": false },
{ "query": "How do we raise money through GitHub Sponsors for our project?", "should_trigger": false },
{ "query": "Design a bottom-up go-to-market motion for our developer tool.", "should_trigger": false },
{ "query": "Plan our integrations and partner ecosystem strategy.", "should_trigger": false },
{ "query": "Design a live demo that won't break on stage.", "should_trigger": false },
{ "query": "Which of your developer relations skills should I use for this task?", "should_trigger": false },
{ "query": "Optimize our docs so coding agents can consume them reliably.", "should_trigger": false },
{ "query": "Write a v2 to v3 migration guide for our API.", "should_trigger": false },
{ "query": "Write a customer case study about how Acme uses our API.", "should_trigger": false },
{ "query": "Apache 2.0 or AGPL for our new project?", "should_trigger": false },
{ "query": "Should we publish to npm, Homebrew, or both?", "should_trigger": false },
{ "query": "Improve our employer brand so more engineers apply to us.", "should_trigger": false },
{ "query": "Open core or hosted? Help me pick a business model.", "should_trigger": false },
{ "query": "How do we structure a company around an open-source project?", "should_trigger": false },
{ "query": "Set standards for the code samples in our docs.", "should_trigger": false },
{ "query": "Write a troubleshooting page covering our top ten errors.", "should_trigger": false },
{ "query": "Make it easier for first-time contributors to land a pull request.", "should_trigger": false },
{ "query": "Design sponsorship tiers for our open-source project's sponsors page.", "should_trigger": false },
{ "query": "Research the market size for API observability tools.", "should_trigger": false },
{ "query": "Which agent skills exist for marketing work?", "should_trigger": false },
{ "query": "Set up an RSS reader and organise my feeds into folders.", "should_trigger": false },
{ "query": "Summarise this week's Hacker News front page for me.", "should_trigger": false },
{ "query": "Write a weekly newsletter for the developers who use our product.", "should_trigger": false },
{ "query": "Start a podcast for our devtool company - format, cadence, guest pipeline.", "should_trigger": false },
{ "query": "Which AI newsletters should I read to keep up with LLM research?", "should_trigger": false },
{ "query": "Build a competitive intelligence tracker for three rival devtools.", "should_trigger": false },
{ "query": "What conferences do our target developers attend, so we know where to buy booths?", "should_trigger": false },
{ "query": "Benchmark our Discord against our competitors' communities.", "should_trigger": false },
{ "query": "Write my personal brand strategy as a developer advocate.", "should_trigger": false },
{ "query": "Design the interview loop for a DevRel manager role.", "should_trigger": false },
{ "query": "Recommend a reading list on distributed systems.", "should_trigger": false },
{ "query": "What books should I read to become a better engineering manager?", "should_trigger": false },
{ "query": "Help me choose a CRM for our partner program.", "should_trigger": false },
{ "query": "Analyse our competitor's documentation and tell me where ours is weaker.", "should_trigger": false },
{ "query": "Set up alerting so I know when someone mentions our product on social media.", "should_trigger": false },
{ "query": "Monitor these five vendor blogs and email me whenever they publish.", "should_trigger": false },
{ "query": "Draft a sponsorship prospectus for the meetup we host.", "should_trigger": false },
{ "query": "Plan the agenda and track structure for our first developer conference.", "should_trigger": false },
{ "query": "Find speakers for our online developer summit.", "should_trigger": false },
{ "query": "What's a good OKR set for a DevRel team?", "should_trigger": false },
{ "query": "Review our developer onboarding email sequence.", "should_trigger": false },
{ "query": "Which SEO tools should I subscribe to?", "should_trigger": false },
{ "query": "Compare the community analytics tools on the market for us.", "should_trigger": false },
{ "query": "Write a press release announcing our Series B.", "should_trigger": false },
{ "query": "Explain what the four DevRel pillars mean.", "should_trigger": false }
]
}
references/people-to-follow.md›
# DevRel people to follow
DevRel conversation lives largely on short-post and professional social networks, which block automated checking, so nobody below is verified through a social profile. Each person was confirmed (or not) through a **fetchable surface**: a podcast feed or episode page, a company site, a talk listing, a practice hub.
A handle recorded anywhere is _as stated on that page_, never independently verified. A parked or DNS-dead personal domain makes a person **unverified with the reason**, never inactive: one well-known agency founder's personal domain sits on a for-sale page while his company publishes weekly.
Nearly everyone sells something: consulting, an agency, a course, a startup, or the platform itself. The disclosure column exists so the reader can weigh advice, not to disqualify anyone.
| Name | Topic | Pillar | Verifying surface | What they're selling | Cross-surface recurrence | Status + date |
| -------------------------------- | --------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Mary Thengvall | DevRel practice, community, curation | advocacy, community | Community Pulse Ep 105, 17 Aug 2026; marythengvall.com lists DevRel Weekly, the podcast and her book (no dates on site) | consulting (Persea) | strong: newsletter curator + podcast co-host + author | active, 2026-08-26 |
| Wesley Faulkner | DevRel strategy, community, neurodiversity in tech | advocacy, community | wesleyfaulkner.com - upcoming talk listed 28 Oct 2026; states he chaired the DevRel Foundation through Jul 2026, which the Foundation's own governance repo corroborates (the former Steering Committee stood down in the Aug 2026 transition) | advisory/consulting | strong: two podcasts + speaking + org leadership | active, 2026-08-28 |
| Jayson DeLancey | DevRel practice organisation, security advocacy | all four | GitHub `@j12y` - named project lead on four Developer Relations Foundation projects; profile states Head of Security Advocacy at Semgrep and DRF Steering Committee | employer + foundation role | foundation projects + employer surface | active, 2026-08-28 - the DRF Steering Committee he sat on has since stood down; his project leadership is what to track |
| Arun Gupta | DevRel measurement, open-source programme offices | advocacy, community | GitHub `@arun-gupta` - lead of the DRF Metrics Index project; profile updated 23 Aug 2026, states NVIDIA | employer + foundation role | foundation project + long-running speaking record | active, 2026-08-28 |
| Matthew Revell | The practice's canon: four pillars, CORE, developer journey | all four | hoopy.io wind-down notice (© 2026) + developerrelations.com guides and podcast series | practice hub (agency now closed) | strong: DevRelCon founder + hub publisher + podcast host | active, 2026-08-26 - the agency closed; the person and the hub did not |
| PJ Hagerty | DevRel and community practice | advocacy, community | Community Pulse Ep 105, 17 Aug 2026 | not determined | podcast only | active via podcast, 2026-08-26 - devrelate.com is DNS-dead; do not link it |
| Jason Hand | DevRel, developer content | advocacy | Community Pulse Ep 105, 17 Aug 2026 | not determined | podcast only | active via podcast, 2026-08-26 |
| Tessa Kriesel | Developer GTM, treating DevRel as a revenue function | advocacy, marketing | tessakriesel.com - post 31 Jul 2026 | consulting/advisory | blog + advisory practice | active, 2026-08-26 |
| Adam DuVander | Technical content strategy for developer products | marketing, enablement | everydeveloper.com - weekly newsletter, books 2021 and 2023, page asset dated 12 May 2026 | agency + books | strong: books + newsletter + agency | active, 2026-08-26 - no individual dated post confirmed |
| Jack Bridger | Devtool growth, DevRel and developer marketing interviews | marketing | Scaling DevTools feed - Ep 197, 20 Aug 2026 | podcast + community | 197 episodes is the durability signal | active, 2026-08-26 |
| Emily Omier | Open-source positioning and business models | community, marketing | emilyomier.com/podcast - 18 Aug 2026 | positioning consulting | podcast + consulting | active, 2026-08-26 |
| Brian Douglas | Open-source community and maintainer tooling | community | Open Source Ready Ep 41, 30 Jul 2026 (Heavybit) | startup (Paper Compute) | podcast + company | active, 2026-08-26 |
| John McBride | Open-source engineering and community | community | Open Source Ready Ep 41, 30 Jul 2026 | startup (Paper Compute) | podcast + company | active, 2026-08-26 |
| Karl Hughes | Technical content operations at scale | marketing | draft.dev - 2026 posts; he is not named on the fetched pages | content agency | agency output only | active via company, 2026-08-26 - karlhughes.com is a for-sale parking page; never link it |
| Ashley Willis | Developer advocacy leadership at a major code host | advocacy | ashley.dev - role and interests stated, no dated posts rendered | employer surface | single surface | active with a weak signal, 2026-08-26 |
| Cassidy Williams | Developer content and newsletter craft | marketing | cassidoo.co/newsletter - weekly cadence claimed, no issue date rendered | newsletter + courses | newsletter + speaking | active with a weak signal, 2026-08-26 - cadence claim unconfirmed by a dated issue |
| Carmen Huidobro | DevRel practice, book-club discussions | all four | developerrelations.com/podcasts - co-host credit, no dates | not determined | single undated surface | unverified for recency, 2026-08-26 |
| Jono Bacon | Community strategy and governance; two widely-read books | community | jonobacon.com - newest post 17 Jan 2025 | masterclass/consulting | books + blog + video | stale (~19 months), 2026-08-26 - read the books, don't count on the feed |
| Mike Schwartz | Open-source company business models | community | opensourceunderdogs.com - Ep 70, 31 May 2024 | podcast + company | podcast only | stale (~27 months), 2026-08-26 |
| Atsushi Nakatsugawa (中津川篤司) | DevRel practice and community organizing in Japan | all four | devrel.tokyo/japan-2024/ - confirmed as a 2024 conference speaker; MOONGIFT CEO, running a DevRel consultancy since 2014 | consultancy (MOONGIFT) | strong: DevRelCon + DevRel Summit + founded the Tokyo chapter + consultancy | active via conference record, 2026-09-10 - no personal blog date confirmed |
| Channy Yun | Korean DevRel practice (AWS background) | advocacy | channy.creation.net - a post exists, but it is old | not determined (former AWS) | single surface, weak | unverified for recency, 2026-09-10 - treat as a name to check current activity for, not a confirmed active blog |
| Aditya Oberai | Developer advocacy and DevRelCon organizing in India | advocacy, community | newsletter.oberai.dev - Developer Advocate @ Appwrite, co-organizer of DevRelCon Bengaluru | employer (Appwrite) + newsletter | strong: newsletter + employer + conference organizing | active, 2026-09-10 - Microsoft MVP, about 1000 newsletter subscribers (stated) |
| Ram Iyengar | DevRel and evangelism leadership, cloud-native (India) | advocacy | Confirmed as a DevRelCon Bengaluru 2024 speaker; Chief Evangelist, Cloud Foundry Foundation | employer + foundation role | conference speaking + foundation role | active, 2026-09-10 - confirmed via Dec 2024 conference speaker record |
| Jimmy Song (宋净超) | DevRel team structure, roles and growth strategy (China) | advocacy, community | jimmysong.io/blog/thinking-devrel/ - no date rendered, described as roughly a year old | not determined | single surface (blog) | stale, 2026-09-10 |
| tisonkun | DevRel-qualified-leads metrics (China) | marketing | tisonkun.org/2024/01/26/devrel-qualified-leads/ - dated 26 Jan 2024 | not determined | single surface (blog) | stale (~31 months), 2026-09-10 |
| 林旅强 (Richard Lin) | Open-source community leadership and DevRel translation (China) | community | Confirmed as a June 2025 Dev.Together speaker; open-source community co-founder, RTE developer community lead, translator of the Chinese edition of a DevRel methods-and-practices book | not determined | conference speaking + book translation + community leadership | active via conference record, 2026-09-10 |
| Jorge Barrachina Gutiérrez | DevRel in Spain and Latin America, book author | all four | Author of _DevRel Puzzle_ (Spanish, 2023); ran webinars on "el futuro del DevRel en España y Latinoamérica"; organized a Madrid meetup | book + consulting/webinars | book + webinars + meetup organizing | stale (~3 years), 2026-09-10 - confirmed activity dates to roughly 2022-2023, current status not confirmed |
| Pachi Parra | DevRel consultancy and Portuguese-language content in Brazil | all four | abacatedevrel.com.br - founder of Abacate DevRel / Abacate Tech; Developer Advocate at GitHub | consultancy (Abacate DevRel) + employer (GitHub) | strong: consultancy founder + dev.to series + employer | stale (~9 months), 2026-09-10 - dev.to series and blog posts confirmed running through December 2025 |
## How to use this list
- Match the Pillar column to the pillars the user actually owns; a depth-focused user gets 3-5 people on their pillars, not the whole table.
- Rank by cross-surface recurrence - the same person as podcast host, conference speaker, and hub author predicts continued relevance far better than any follower count, which is unobservable here anyway.
- Before linking any personal domain, confirm the page's content is about developer relations. Two entries above have personal domains that are parked or DNS-dead while the person publishes elsewhere.
- To find people beyond this table, mine the fetchable high-yield surfaces:
- Podcast guest archives.
- Conference speaker rosters.
- The practice hub's guide bylines.
- Community leadership pages.
- For anyone working inside an open foundation, the code host, where project-lead tables name people and commit dates prove they are still active.
Vendor and agency blogs cite practitioners in research posts as a secondary layer.
- Treat a role change as a source change: someone who moves from a devtool to a platform vendor keeps the expertise but changes the incentive. Re-read the disclosure column at every refresh.
references/sources.md›
# DevRel source list
Each entry carries the date its liveness was last confirmed, so staleness is visible at a glance.
Statuses:
- **active**: dated item ≤ ~3 months old when confirmed.
- **stale**: reachable, newest dated item > ~6 months.
- **unverified**: the fetch failed, or the page renders no dates (reason recorded, never assumed dead).
- **dead**: parked, resold, or non-resolving on every surface it has.
"not stated" means the source publishes no audience figure - do not invent one. "What they're selling" discloses the incentive: almost nothing in this field is conflict-free, so the flag exists for disclosure, not disqualification.
Pillar column maps to the four DevRel pillars: advocacy, marketing, enablement (docs/DX), community. Re-verify anything here before recommending it (see SKILL.md, Freshness and ownership check).
## Table of Contents
- [Practice hubs and evergreen references](#practice-hubs-and-evergreen-references)
- [Podcasts](#podcasts)
- [Newsletters, blogs and trade media](#newsletters-blogs-and-trade-media)
- [Communities](#communities)
- [Events](#events)
- [Data and benchmark sources](#data-and-benchmark-sources)
- [Regional and non-English-language sources](#regional-and-non-english-language-sources)
- [Video](#video)
- [Removed as dead, resold or unreachable](#removed-as-dead-resold-or-unreachable)
## Practice hubs and evergreen references
Undated by nature - these are reference works, not feeds. Judge them on maintenance signals, never on cadence.
| Name | URL | Who's behind it | Best for | Pillar | Last confirmed | Price | What they're selling | Status + reason |
| ------------------------------ | ----------------------------------------------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | --------------------------------------------------------------------------------------------- | ----- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| DeveloperRelations.com | developerrelations.com | Hoopy Limited (Matthew Revell) | The field's practice canon: 21 guides (four pillars, CORE framework, friction logging, champion programs, developer journey), DevRelCon talk archive, newsletter, three podcast series | all four | © 2015-2026; lists DevRelCon New York 22-23 Jul 2026 | free | practice hub (former agency) | active - guides render no dates; the site survives its founding agency's wind-down |
| Hoopy | hoopy.io | Matthew Revell | Context on who now owns what: the agency ran 2016-2026 and handed DevRelCon to Major League Hacking | all four | © 2026 wind-down notice | free | nothing (closed) | active as a notice, not as a feed |
| Developer Relations Foundation | dev-rel.org (org: github.com/DevRel-Foundation) | The Linux Foundation, as a hosted community project | The field's only vendor-neutral practice body: open Metrics Index, DevRel Maturity Model, Tools Catalog, Persona Library; public governance and meeting notes | all four | governance repo commit 28 Aug 2026; bi-weekly Community Touchpoint calls announced from 2 Sep | free | nothing (foundation) | `verified-active`, transition confirmed complete via search - Steering Committee elections were held November 2025 (per the DRF's own staggered-election governance model: even years elect 2 seats + 1 appointed), so a seated committee has been in place since; four working groups self-declaring "no longer active" may still be genuinely dormant |
| Open Source Guides | opensource.guide | GitHub | Maintainer-side guides: governance, code of conduct, security, maintainer burnout, best practices | community | none rendered | free | platform-official | unverified for date - evergreen reference, treat as maintained |
| Diátaxis | diataxis.fr | not stated on the fetched page | The tutorial / how-to / reference / explanation split that docs audits are run against | enablement | none rendered | free | none visible | unverified for date - evergreen framework |
| CHAOSS | chaoss.community | Linux Foundation project | Open metric definitions and models for community health, plus practitioner guides and tooling | community | newsletter 18 Sep 2025; CHAOSScon 2026 EU announced without a date | free | foundation project | active but slowing - newest dated item ~11 months old |
## Podcasts
Feeds beat homepages for dates here; two shows below were only datable through a feed or an episode page.
| Name | URL | Who's behind it | Best for | Pillar | Last confirmed | Price | What they're selling | Status + reason |
| ------------------------------------------------------------------ | ----------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------- | --------------------------------------------- | ----- | ---------------------- | ---------------------------------------------------------------------------------------------------------- |
| Community Pulse | communitypulse.io | Mary Thengvall, PJ Hagerty, Wesley Faulkner, Jason Hand | The one long-running show about the DevRel practice itself | advocacy, community | Ep 105 "Let Me Tell You a Story", 17 Aug 2026 | free | hosts' consulting | active |
| Scaling DevTools | feeds.transistor.fm/scaling-devtools | Jack Bridger | Devtool growth interviews: DevRel, developer marketing, DX, founders | marketing, advocacy | Ep 197, 20 Aug 2026 | free | community/sponsorships | active - the site 403s to automated fetchers; the feed is the datable surface |
| Open Source Ready | heavybit.com/library/podcasts/open-source-ready | Brian Douglas, John McBride | Open-source ecosystem, maintainer economics, tooling | community | Ep 41, 30 Jul 2026 | free | hosts' startup | active |
| The Business of Open Source | emilyomier.com/podcast | Emily Omier | Positioning and monetising an open-source project | community, marketing | 18 Aug 2026 | free | consulting | active |
| Heavybit Podcast Network | heavybit.com/library/podcasts | Heavybit | 28 shows for developer-facing companies (Developer Love, Jamstack Radio, O11ycast, The Secure Developer, Generationship…) | marketing, enablement | network confirmed via one show, 30 Jul 2026 | free | VC firm's content arm | active as a network - episode counts only, no per-show dates: check each show's own page before listing it |
| DevRel Roundtable / DevRel Book Club / Developer Marketing Stories | developerrelations.com/podcasts | Matthew Revell, Carmen Huidobro and guests | Practice-specific panels and book discussions | all four | none rendered | free | practice hub | unverified for recency - directory page shows no episode dates |
| Open Source Underdogs | opensourceunderdogs.com | Mike Schwartz | Open-source company business models | community | Ep 70, 31 May 2024 | free | host's company | stale (~27 months) - list only if the user accepts an archive |
## Newsletters, blogs and trade media
| Name | URL | Who's behind it | Best for | Pillar | Last confirmed | Audience | Price | What they're selling | Status + reason |
| ----------------- | --------------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ------------ | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| DevRel Weekly | devrelweekly.com | Mary Thengvall | The field's canonical curated link roundup | all four | Confirmed via search: the curator posted her own wind-down announcement directly on the site (not an infrastructure failure) - Twitter/X platform changes broke the RSS-based workflow the newsletter relied on, so the strict "Weekly" cadence is ending, replaced by an occasional "DevRel Thoughts Shared Randomly" format | not stated | free | curator's consulting | `verified` but format-changed - list it as sporadic/occasional going forward, not weekly; the 525 errors reflected the site mid-transition, not death |
| DevRel Newsletter | developerrelations.com/newsletter | Hoopy | DevRel, dev marketing, DX and community links | all four | none - signup page, no archive | "thousands of DevRel professionals" (claimed) | free | practice hub | unverified for cadence - property itself is active |
| Console.dev | console.dev | Console | Weekly developer-tool reviews; doubles as a channel DevRel teams pitch | marketing | 20 Aug 2026 | "30k+ subscribers" (stated) | free | sponsorships | active - every Thursday |
| EveryDeveloper | everydeveloper.com | Adam DuVander | Technical content strategy for dev-focused companies; author of two developer-marketing books (2021, 2023) | marketing, enablement | page asset dated 12 May 2026; `/articles/` 404s | not stated | free content | agency + books | active - no individual dated post confirmed |
| Draft.dev | draft.dev/learn | Draft.dev (founded by Karl Hughes; not named on the fetched page) | Technical content marketing, devtool GTM, agent-ready content | marketing | 2026 posts incl. a Common Room acquisition breakdown | "over 3,000 subscribers" (newsletter, stated) | free content | content agency | active |
| Tessa Kriesel | tessakriesel.com | Tessa Kriesel | Developer GTM, "DevRel is sales", adoption intelligence | advocacy, marketing | 31 Jul 2026 | not stated | free | consulting/advisory | active |
| The New Stack | thenewstack.io | not stated on the fetched page | Daily developer-ecosystem news - the budget compressor when time is tight | all four | 26 Aug 2026 | not stated | free | ad-supported media | active |
| Common Room blog | commonroom.io/blog | Common Room (acquired by Zoom per a 2026 Draft.dev breakdown) | Signal-based GTM; historically the source of DevRel measurement and compensation research | marketing | 24 Aug 2026 | not stated | free content | tool vendor | active but re-angled - the DevRel-specific research it was cited for is no longer its focus |
| Jono Bacon | jonobacon.com | Jono Bacon | Community strategy essays; author of _People Powered_ and _The Art of Community_ | community | 17 Jan 2025 | not stated | freemium | masterclass/consulting | stale (~19 months) - books stay useful, the blog is not a feed |
## Communities
Application gates and chat walls make every membership figure a self-reported claim. None can be verified from outside.
| Name | URL | Who's behind it | Best for | Pillar | Last confirmed | Audience | Price | What they're selling | Status + reason |
| ------------------------------ | ----------------------------------------------------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------ | --------------------------------------- | ------------------------ | -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| DevRel Collective | devrelcollective.fun | DevRel practitioners | The field's peer Slack - practitioners only, application-gated | all four | join flow live (invites valid ~90 days); no dated item | "over 1,800 professionals" (claimed) | free | nothing visible | active - gated, so activity is unobservable from outside |
| CMX | cmxhub.com | CMX (Bevy) | Community-profession community, Connect events, Academy, annual Community Industry Report (7th edition, 2026) | community | Loop 2026 online 25-26 Aug 2026 | not stated | freemium (paid Academy) | training + platform | active |
| Write the Docs | writethedocs.org | Write the Docs community | Documentarians' Slack and conference series - the docs/DX peer network | enablement | conferences listed through May 2027 | "thousands of documentarians" (claimed) | free (conf tickets paid) | conference tickets | active |
| DRF community list and Discord | lists.dev-rel.org/g/community (calendar at /g/community/calendar) | Developer Relations Foundation | The open, ungated alternative to the application-gated Slack: mailing list, community calendar, per-project Discord channels, bi-weekly Touchpoint calls timed to overlap APAC/EMEA/AMER | all four | Touchpoint restart announced for 2 Sep 2026 (governance discussion #166) | not stated | free | nothing (foundation) | active - the `dev-rel.org/calendar` page renders "Loading events…" to a fetcher; subscribe on the list server instead |
| r/devrel | reddit.com/r/devrel | Reddit community | Open Q&A on the practice | all four | none - fetch refused | not stated | free | none | unverified - this forum platform blocks automated checking; says nothing about the community, check it manually |
## Events
The most reliably dated surface in the field. Confirm the organiser as well as the date - one flagship recently changed hands. The Developer Relations Foundation's Events Directory (github.com/DevRel-Foundation/events-directory) is the field's attempt at a shared CFP/sponsorship calendar, but the repository is still a stub - track it, don't cite it.
| Name | URL | Who's behind it | Best for | Pillar | Confirmed dates | Price | Status + reason |
| ------------------------------ | --------------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| DevRelCon | developerrelations.com (New York edition at nyc.devrelcon.dev) | Major League Hacking (handed over by Hoopy in 2026) | The field's own conference | all four | New York 22-23 Jul 2026, at Industry City Brooklyn, mini-hackathon the evening of Jul 21 - independently confirmed via search (dev.to/mlh's own announcement post), including the direct MLH connection via DEV's absorption into MLH | confirmed via MLH's own announcement | `verified-active`, organiser and date confirmed independently - about 300 attendees, 2026 programming themed on AI's effect on DevRel |
| Write the Docs | writethedocs.org | Write the Docs | Docs and DX practice | enablement | Nairobi 8 Aug 2026; Berlin 6-8 Sep 2026; Melbourne 3-4 Dec 2026; Portland 2-4 May 2027 | tickets, price not fetched | active |
| WeAreDevelopers World Congress | wearedevelopers.com/world-congress | WeAreDevelopers | Reaching a large general developer audience; sponsorship/booth planning | marketing, advocacy | Berlin 14-16 Jul 2027 | Congress Pass €329 early-bird (regular €799) | active - "15,000+ builders, 500+ speakers" claimed |
| CMX Loop | cmxhub.com | CMX (Bevy) | Global community-profession summit, online | community | 25-26 Aug 2026 (online); CMX Summit 2027 announced | not fetched | active |
| KubeCon + CloudNativeCon NA | events.linuxfoundation.org/kubecon-cloudnativecon-north-america | CNCF / Linux Foundation | Cloud-native ecosystem presence, CFP target, booth strategy | advocacy, marketing | Salt Lake City, 9-12 Nov | not fetched | active - year not rendered on the page; confirm before booking |
| DeveloperWeek | developerweek.com | Informa Connect | Large developer conference with a DevRel/dev-exec track | marketing | none - HTTP 403 | not fetched | unverified - bot-block, not evidence of death |
| Major League Hacking | mlh.com | MLH | Student/hackathon ecosystem reach; now also DevRelCon's owner | community, advocacy | "2026 hackathon season", 1,000+ events/yr claimed | free to sponsor-gated | active - its own homepage does not mention DevRelCon, so confirm the handover on the event's page before quoting it |
## Data and benchmark sources
First-class in DevRel: the practice is defended upward with numbers the team does not own. Cite the edition and its date, never a bare statistic.
| Name | URL | Who's behind it | Best for | Last confirmed | Price | Status + reason |
| -------------------------------------- | ----------------------------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------------------- | ------------------------------------------------------------------------------------------------------- |
| GitHub Octoverse | github.blog/news-insights/octoverse | GitHub | Annual open-source and language-ecosystem trends | Octoverse 2025 published 28 Oct 2025 | free | active annual |
| JetBrains State of Developer Ecosystem | devecosystem-2025.jetbrains.com | JetBrains | Tooling and workflow adoption; 24,534 respondents, fielded Apr-Jun 2025 | 2025 edition | free | active annual |
| Stack Overflow Developer Survey | survey.stackoverflow.co | Stack Overflow | Broad developer demographics, tooling and sentiment; archives back to 2011 | 2025 edition; no publication date rendered | free | active annual, date unconfirmed |
| SlashData | slashdata.co (developer panel at developernation.net) | SlashData | Quarterly developer population sizing and ecosystem insights - the closest thing to analyst coverage of developer segments | blog post dated Q3 2026 | free summaries, paid reports | active - `/reports` 404s, navigate from the homepage |
| DRF Metrics Index | github.com/DevRel-Foundation/metrics-index | Developer Relations Foundation (lead: Arun Gupta) | Open, contributable definitions of DevRel metrics with collection and benchmarking advice - the vendor-neutral counterpart to a vendor's measurement blog | last push 9 Jan 2026 | free | active but early - v0.0, "sandbox" lifecycle; treat as a definitions reference, not a benchmark dataset |
| CMX Community Industry Report | cmxhub.com | CMX (Bevy) | Community-profession benchmarks: budgets, team sizes, measurement | 2026 edition, "seventh annual" | free (gated) | active annual |
## Regional and non-English-language sources
The tables above skew English-language and US/UK-centric. This section covers non-English-language, APAC-region and EU-local-language sources found through a dedicated discovery sweep, grouped by type like every other section. Treat it as a solid, verified starting set, not an exhaustive census: a full non-English/APAC/EU sweep spans 9+ languages across 5 categories, more than a handful of search passes can cover completely.
### Communities (regional)
| Name | URL | Region/Language | Who's behind it | Pillar | Last confirmed | Status + reason |
| ------------------------------------------------------ | ------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| DevRel/Tokyo | devrel.tokyo (Slack) + devrel.connpass.com (event group) | Japanese, Japan | DevRel/Tokyo community | community | ~600 members, a May 2021 site figure | unverified - the membership figure is from 2021; the companion podcast below is active through Aug 2026, so the community around it is likely alive, but the Slack itself has no independent recent date |
| Devchat (데브챗) | no public URL confirmed - SK Telecom-backed study/networking group | Korean, Korea | Practitioners from SKT, Naver, Line, Samsung, Lotte e-commerce, LG Uplus, Genie Music and others | community | confirmed activity ~2022 | stale - current cadence not confirmed, verify before relying |
| DEVOCEAN (데보션) | devocean.sk.com / dev.sk.com | Korean, Korea | SK Telecom / SK AX | advocacy, community | posts dated 8 Apr 2026 and 20 Mar 2026 | active - company-run platform, not independent; monthly newsletter, community board, expert interviews, recurring "데보션 테크 데이" events (6th edition drew 102 developers) |
| The DevRel Salon (Paris / Amsterdam / Lisbon chapters) | devrel.salon | French (Paris), Dutch (Amsterdam), Portuguese (Lisbon, planned) | DevRel Salon organizers | all four | none rendered | unverified - the official site describes the format as currently running in Paris and Amsterdam with Lisbon planned; a separate podcast source called the Paris chapter "aujourd'hui inactive" - conflicting signals, verify directly |
| DevRelAms / DevRel Amsterdam | meetup.com/DevRelAms | English (Netherlands) | DevRelAms organizers | community | founded 2015 | stale - about 35 members, occasional "DevRel Lunch" events, low visible recent activity |
| Developer Relations Munich | meetup.com/Dev-Rel-Munich | English (Germany) | Munich DevRel meetup organizers | community | most listed events from 2019 | stale - 526 members, featured in t3n magazine's August edition; no dedicated German-language DevRel source found in this market (see Confirmed gaps) |
| Berlin Developer Relations Meetup | via Meetup.com topics page | English (Germany) | Berlin DevRel meetup organizers | community | none rendered | unverified - 286 members per current listing, event cadence not confirmed; no dedicated German-language DevRel source found in this market (see Confirmed gaps) |
| Abacate DevRel / Abacate Tech | abacatedevrel.com.br | Portuguese, Brazil | Pachi Parra, Developer Advocate at GitHub | all four | dev.to series and blog posts running through Dec 2025 | stale (~9 months) - Brazil's pioneering DevRel consultancy, explicitly framed as filling a gap ("falta conteúdo em português" on DevRel); reverify current cadence before relying |
### Podcasts (regional)
| Name | URL | Region/Language | Who's behind it | Pillar | Last confirmed | Status + reason |
| ----------------------------- | ------------------------------------- | --------------- | ---------------------- | ---------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| DevRel/Radio (デブレルラジオ) | via devrel.connpass.com | Japanese, Japan | DevRel/Tokyo community | advocacy, community | Ep #279, 18 Aug 2026 | active - weekly cadence |
| Developer Experience | podcast.ausha.co/developer-experience | French, France | Donatien Léon | all four | Ep 108, 3 Jul 2026 | active - biweekly cadence, rated 5/5 over 15 Apple Podcasts reviews |
| Gitbar | gitbar.it | Italian, Italy | Gitbar hosts | general developer culture, not DevRel-specific | Ep 238, 23 Jun 2026 | active - closest verified Italian-language match; ran one dedicated DevRel episode (Ep 152, with Mattia Tommasone of Google) but is not a DevRel-focused show |
### Blogs (regional)
| Name | URL | Region/Language | Who's behind it | Pillar | Last confirmed | Status + reason |
| ------------------- | ----------------------------------------------- | --------------- | --------------- | ------------------- | ------------------------------------------------- | --------------------------------------------------------------- |
| Jimmy Song (宋净超) | jimmysong.io/blog/thinking-devrel/ | Chinese, China | Jimmy Song | advocacy, community | no date rendered, described as roughly a year old | stale - covers DevRel team structure, roles and growth strategy |
| tisonkun | tisonkun.org/2024/01/26/devrel-qualified-leads/ | Chinese, China | tisonkun | marketing | 26 Jan 2024 | stale (~31 months) - covers DevRel-qualified-leads metrics |
### Events (regional)
| Name | URL | Region/Language | Who's behind it | Pillar | Confirmed dates | Status + reason |
| ----------------------------- | ------------------------------------------------------------------------------------- | ----------------------- | ------------------------------- | ------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| DevRel/Japan CONFERENCE | devrel.tokyo/japan-2024/ | Japanese, Japan | DevRel/Tokyo community | all four | annual since 2019, confirmed through 2024 | unverified for current year - Japan's only Japanese-language DevRel conference; check the site for a 2026 date |
| Dev.Together (开发者生态峰会) | bagevent.com/event/devtogether-2025 (organiser: github.com/segmentfault/dev-together) | Chinese, China | SegmentFault | community | June 2025 edition, 30+ speakers | stale for current year - confirmed active 2025 edition covering AGI, Web3 and open-source ecosystem topics; 2026 edition not confirmed |
| DevRelCon Bengaluru | blr24.devrelcon.dev | English, India | Global DevRelCon series | all four | first edition Dec 2024 | stale - part of the same series also running in Latin America, Prague, San Francisco, Tokyo and China; follow-up edition not confirmed |
| DevFest Singapore | Google Developer Group event | English, Singapore | Google Developer Group | marketing, advocacy | confirmed for 2024 | unverified for current year - recurs annually as a GDG event with a regional lead for Southeast Asia and South Asia; check for the current year's date |
| DevRelCon Prague | devrelcon.dev | English, Central Europe | Global DevRelCon series (Hoopy) | all four | last confirmed edition Dec 2022 | stale - current cadence not confirmed, check devrelcon.dev directly for a 2026 date |
| DevRelCon China | devrelcon.dev | English/Chinese, China | Global DevRelCon series (Hoopy) | all four | none confirmed | unverified - confirmed to exist as a series edition per Hoopy's own materials, no specific recent-year edition page found |
| DevFest.cz | general developer conference, not DevRel-specific | Czech, Central Europe | DevFest.cz organizers | marketing | next edition 30 Oct 2026 | active - useful as a regional calendar anchor even though it is not DevRel-focused |
### Confirmed gaps (searched, not found)
- **Nordic languages** (Swedish, Norwegian, Danish, Finnish): the only concrete find was a Stockholm "Developer Relations Sweden" meetup, last confirmed activity 2020, appears dormant. No active Nordic-language podcast, newsletter or community found.
- **Polish language**: no dedicated DevRel-specific podcast, newsletter or community found. `4developers.org.pl` is a large, active general Polish developer conference, not DevRel-focused, so it does not fit here.
- **German language** (as opposed to Germany-located, English-language groups): no dedicated German-language DevRel podcast, newsletter or blog found. Both the Munich and Berlin meetups above run in English despite their location.
- **Chinese Slack/Discord/forum community**: not found, and this is structural rather than a missed search - Slack and Discord are both largely inaccessible inside mainland China, so Chinese DevRel communities run on WeChat and QQ groups instead, which are not searchable or joinable from outside without an existing invite.
## Video
Video platforms answer an automated fetcher with a consent wall (302 to a consent domain), so subscriber counts and upload dates are not observable that way. Do not list a channel on memory alone. DevRelCon talks are also published on developerrelations.com, which is fetchable; prefer that surface and label any channel entry "corroborated via a companion surface; channel itself unobserved".
## Removed as dead, resold or unreachable
Each of these looks plausible and is not usable:
- **devrelx.com** - resold: 301s to `showmebrewing.com`, an unrelated business. The link resolves, which is exactly why this failure ships silently. Never link it.
- **karlhughes.com** - parked on a domain-marketplace for-sale page, while its owner's agency (draft.dev) publishes actively. A dead personal domain says nothing about the person.
- **devrelfoundation.org / devrel.foundation** - both DNS-dead, and both are plausible-looking guesses rather than the real domain. The Developer Relations Foundation is alive at **dev-rel.org**, reachable by searching the code host for the organisation name, and it is listed in the practice-hub, community and data sections above. A guessed domain returning NXDOMAIN is evidence about the guess, never about the organisation.
- **orbit.love** - HTTP 530, no reachable content; the community-analytics category has consolidated into GTM-intelligence vendors.
- **developermarketing.io** (Developer Marketing Alliance) - 301s to `productmarketingalliance.com`, which shows no developer-marketing brand at all. Treat as absorbed and dropped; not listed.
- **devrelate.com** - DNS failure.
- **console.dev/podcast** and **/podcasts** - both 404; the show is referenced on the newsletter's homepage but has no reachable page of its own.
- **everydeveloper.com/articles/** - 404; the site is alive, that path is not.
references/watch-list-example.md›
# Worked example and negative example
## Worked example
Interview answers:
- Solo developer advocate at a Series A API company.
- Owns advocacy, enablement (docs) and part of marketing; no community pillar yet.
- 60 minutes a week.
- Audio plus text, no video.
- B2B devtool sold bottom-up to backend engineers.
- Breadth over depth.
- Wants vendor incentives flagged but not filtered.
---
**DevRel radar - solo advocate, API devtool, B2B**
Pillars owned: advocacy, enablement, marketing (no community pillar). Budget: 60 min/week. Verified: 2026-08-26.
**Weekly core - 52 min.** Ordered by value per attention-minute, highest ratio first: text skims cost minutes and buy what happened; the two podcasts cost most of an hour each and buy the reasoning behind it, so by default they lose the budget round. Commute listening halves their cost and is what promoted them into the list - the re-rank, stated rather than implied.
| Source | URL | Medium | Pillar | Min | Why it earned the slot | Selling | Status |
| ---------------- | ------------------------------------ | ---------- | --------- | ------------------------------ | -------------------------------------------------------------------------------------- | -------------------- | -------------------------- |
| The New Stack | thenewstack.io | news site | all | 10 (skim) | Budget compressor - one daily source replaces following five vendor blogs | ad-supported media | active, 26 Aug 2026 |
| Console.dev | console.dev | newsletter | marketing | 7 | Shows how devtools get positioned to developers, and is a channel you can pitch | sponsorships | active, 20 Aug 2026 |
| Community Pulse | communitypulse.io | podcast | advocacy | 20 (halved: commute listening) | The only long-running show about the practice itself; four hosts means four ecosystems | hosts' consulting | active, Ep 105 17 Aug 2026 |
| Scaling DevTools | feeds.transistor.fm/scaling-devtools | podcast | marketing | 15 (halved) | Founder-level devtool growth interviews; nearest thing to a devtool GTM archive | podcast/sponsorships | active, Ep 197 20 Aug 2026 |
**Monthly - reference, not a feed**
| Source | URL | Pillar | Why | Status |
| ----------------------------- | ---------------------- | ---------- | ---------------------------------------------------------------------------------------------- | ------------------------------- |
| DeveloperRelations.com guides | developerrelations.com | all | The practice canon: four pillars, CORE, friction logging. Read once, revisit when scoping work | active, undated by design |
| Diátaxis | diataxis.fr | enablement | The framework your docs audit will be run against | evergreen, no dates rendered |
| EveryDeveloper | everydeveloper.com | marketing | Technical content strategy from someone who wrote the two books on it | active, no dated post confirmed |
**Annual - data you will be asked for**
GitHub Octoverse (28 Oct 2025 edition) · JetBrains State of Developer Ecosystem (2025, 24,534 respondents) · SlashData quarterly ecosystem sizing. Each is cited with its edition and date, never as a bare number.
**Events - one CFP target, one attend**
Write the Docs Berlin, 6-8 Sep 2026 (enablement pillar, CFP practice) · KubeCon NA, Salt Lake City 9-12 Nov (confirm the year on the page before booking).
**Bench (verified substitutes)**
The Business of Open Source (18 Aug 2026) · Tessa Kriesel (31 Jul 2026) · Draft.dev (2026 posts).
**Totals** - 52 of 60 weekly minutes; 4 weekly + 3 monthly + 3 annual + 2 events + 3 bench. Verified-active: 11 of 12 listed; 1 evergreen-undated (Diátaxis). Pillar coverage: advocacy ✅, enablement ✅, marketing ✅, community - not owned, deliberately empty. Unverified presented as verified: 0.
**Dropped** - video entirely (medium not consumed), so no conference-talk archive or channel appears anywhere above, bench included. Deleted rather than ranked last, so it does not return as scope at the next refresh.
**Not now** - DevRel Collective Slack (community pillar isn't yours yet; join the month you're asked to start one). DevRel Weekly (site returned an infrastructure error on three paths at verification - retry next refresh before adding).
---
## Negative example - what a failed radar looks like
> **Your DevRel reading list**
> Podcasts: Community Pulse, DevRel Radio, The DevRel Show. Newsletters: DevRel Weekly, DevRelX. Follow: @swyx, @cassidoo, @b0rk, @kelseyhightower. Communities: Orbit Community, Developer Marketing Alliance, r/devrel. Conferences: DevRelCon (Hoopy), DeveloperWeek.
> Should take about an hour a week!
Everything wrong with it, in order of damage:
1. **Invented sources.** "DevRel Radio" and "The DevRel Show" were not observed anywhere in the audit. One fabricated entry costs the reader's trust in all twenty.
2. **A resold domain presented as live.** DevRelX now redirects to an unrelated brewing business. The link resolves, so the mistake is invisible until the reader clicks.
3. **Dead communities.** Orbit returned HTTP 530; the Developer Marketing Alliance's domain now redirects to a product-marketing brand with no developer-marketing presence.
4. **A stale organiser.** DevRelCon is real and alive, but Hoopy handed it to Major League Hacking in 2026 - the date-only check passes while the attribution is wrong.
5. **Social handles as the primary surface.** Those platforms block verification; a handle is at best "as stated on a fetchable page", and a person's relevance to DevRel isn't established by fame in an adjacent field.
6. **No dates, no statuses, no incentive disclosure.** The reader cannot tell what was checked, when, or who is selling what.
7. **A time budget asserted, not computed.** "About an hour" for four podcasts plus five newsletters is roughly three hours; the list is unusable at the stated budget.
8. **No pillar mapping.** Nothing tells a docs-heavy advocate which of these serves enablement, so the list gets skimmed once and abandoned.
9. **A flat list with no ordering.** Twenty entries in arbitrary order hand the reader no way to choose what to open first with the hour they have - and nothing states what was dropped, so every ruled-out source returns as scope next quarter.
SKILL.md›
---
name: devrel-radar
description: Builds a personalised, time-budgeted watch list of developer-relations information sources - DevRel podcasts, newsletters, practice hubs, peer communities, conference calendars, ecosystem data reports and practitioners worth following - plus the routine that keeps it verified and fresh. Use whenever a developer advocate, community manager, DevRel lead or OSS maintainer asks for a DevRel radar, how to stay current on developer relations, which DevRel podcasts, newsletters or Slack communities deserve their time, which developer conferences to attend or speak at, who to follow in DevRel, or to refresh a radar built earlier - even if they only say they feel out of the loop. Not for tracking a rival vendor - use samber/developer-relations-skills@devrel-competitor-analysis.
license: MIT
metadata:
author: Samuel Berthe
version: "1.0.1"
---
# DevRel Radar
You are a curator of the developer-relations information ecosystem. Your deliverable is a personalised watch list that fits the user's weekly time budget, plus the routine that keeps it alive.
Design against two failures:
- **Universal**: dead or stale entries.
- **Field-specific, ownership drift**: DevRel's canon is small and consolidating. Hoopy, the agency that founded both DevRelCon and the practice hub developerrelations.com, wound down in 2026 and handed the conference to Major League Hacking. A widely cited DevRel research brand's domain was resold to an unrelated business. `references/sources.md` records the rest of that audit.
A source can publish weekly and still no longer be the thing the user remembers.
## Method this skill borrows
None of these methods is native to DevRel - they come from education theory, curation practice, digital literacy and library science. Name them only if the user asks why the list is short or personal; the substance matters more than the labels.
- **Personal Learning Network** (connectivism; George Siemens and Stephen Downes): a practitioner learns from a deliberately chosen network, not from consuming everything. Three load-bearing moves are here:
- Declared goals before recommendations (the interview).
- Selectivity over completeness (the time budget).
- Variable relationship strength (ranking, not a flat list).
- **Curation as selection, not indexing.** A curator's value is what they leave out. Rank by cross-surface recurrence and institutional backing. Reject social rating - likes, shares, follower counts - because it measures reach in an adjacent audience rather than standing in this one, and most of it is unobservable here anyway.
- **SIFT** (Mike Caulfield): stop, investigate the source, find better coverage, trace the claim to its origin. Use it for the refresh pass - it is fast enough to re-run on a whole list quarterly.
- **CRAAP's Authority and Purpose** (Sarah Blakeslee, CSU Chico, 2004): who is behind a source, and why do they publish. Use it to vet one new candidate thoroughly. Purpose is what the "what they're selling" flag records.
## Interview
Ask these one at a time. Wait for each answer before the next. Offer the options as written.
1. "What's your role?" - (a) developer advocate / DevRel engineer, (b) community manager, (c) technical writer / docs owner, (d) DevRel lead or manager, (e) OSS maintainer doing this solo.
**Memory: Store a few info about the current task or project context. When memory lives in a file, use `devrel-context.md`; if a different memory system is in use, rely on that instead. Separate task info in different sections. Remove finished tasks. Add a date to a task; no date for general project context. Some interview responses may differ between 2 tasks.**
2. "Which pillars do you actually own? Name all that apply." - advocacy (speaking, content, feedback loop), developer marketing (reach, technical SEO, launches), enablement (docs, SDKs, quickstarts, support), community (platforms, champions, contributors). This answer anchors the coverage requirement below.
3. "How much time per week can you realistically spend staying current?" - (a) under 30 min, (b) 30-60 min, (c) 60-120 min, (d) 2+ hours.
4. "Are you catching up before a specific moment - a first DevRel role, a new ecosystem, a launch, a conference season - or building a standing weekly habit?" - (a) catching up, (b) standing habit.
5. "Which mediums do you actually consume? Pick up to two." - (a) audio, (b) text, (c) video, (d) live community.
6. "Which of those are ruled out entirely - no commute or gym time for audio, a paywall you won't pay, a community or conference you can't expense or can't join?"
7. "Which developer ecosystem are you in?" - e.g. cloud-native/Kubernetes, AI/LLM tooling, web/frontend, data, security, embedded. Ecosystem sources sit next to practice sources, never instead of them.
8. "Who buys and who adopts?" - (a) B2B devtool, bottom-up adoption, (b) B2B enterprise platform, top-down deals, (c) consumer, indie, or education-facing developer product. See B2B and B2C scope.
9. "Do you need to speak, sponsor or organise events this year?" - (a) no, (b) submitting talks, (c) sponsoring or hosting. A yes turns the event calendar from optional to core.
Questions 3, 4, 6 and 9 exist because DevRel's source types diverge sharply on attention cost, on how fast they pay back, and on what they buy - the ordering in step 7 of the workflow cannot be picked for the user without them. Ask them here, in the interview, never beside the ranking. Don't ask for a delivery date: a radar has no deliverable, and question 4 already carries what a deadline would have told you.
## Pillar coverage
Carry at least one verified-active source per pillar the user owns, and none for pillars they don't. A community-heavy list handed to a docs owner is a failed deliverable, not a partial one.
Map candidates with the Pillar column in `references/sources.md`. Where a pillar has no strong practice source, fill it from the field's evergreen references (a docs framework, a maintainer guide) and say plainly that it's a reference work, not a feed.
Add the data family for any user who has to justify budget or headcount: annual ecosystem surveys and open community-health metrics are how DevRel argues impact upward, which makes them a first-class source category here rather than background reading.
## B2B and B2C scope
Most of the field's sources are B2B devtool sources - that is where the money and the podcasts are. Say so rather than implying neutrality.
- **B2B bottom-up devtools**: the default population - practice hubs, devtool growth podcasts, technical content-strategy blogs, developer-tool review newsletters.
- **B2B enterprise platforms**: add the ecosystem's own foundation and conference sources (cloud-native, security, data), where partner and standards work happens.
- **Consumer, indie and education-facing developer products**: the practice sources still apply - pillars don't change - but reach and community sources differ (student/hackathon networks, creator platforms). Verify these separately; the audit behind `references/sources.md` covers the B2B population densely and this one thinly, so tell the user that gap exists instead of padding the list.
## Incentive disclosure
Attach a "what they're selling" flag to every entry: agency, tool vendor, course or community, conference, platform-official, foundation, or independent media. Disclose the incentive; never filter conflicted sources out - that would empty the list, since almost every strong DevRel voice runs an agency, a startup or a paid community.
One exception exists: the Developer Relations Foundation (dev-rel.org, hosted by the Linux Foundation) is the field's only vendor-neutral practice body. Give a user who distrusts vendor content that entry first, and say why it is the exception.
## Video
Video platforms return a consent redirect to any automated check - every channel fetched in this skill's audit did - so a channel cannot be verified the way a feed can. When the user picked video: recommend a fetchable conference-talk archive instead, or name a channel only when a companion surface (the creator's own site, a conference programme) corroborates it, labelled "channel itself unobserved". Never fill the gap with a plausible channel name.
## Personalisation workflow
1. Load `references/sources.md` and `references/people-to-follow.md`. Note the snapshot date in each header - if it is more than ~6 months old (a self-set threshold, like the freshness windows below), tell the user the list needs re-verification before you rely on it.
2. Filter candidates by the interview answers: pillars, mediums, ecosystem, segment, event intent.
3. Delete, don't demote. Drop outright every source question 6 ruled out:
- Audio, when there is no commute or gym time to give it.
- A paywalled newsletter they won't buy.
- A community or conference they can't expense.
- A platform their employer blocks, or that requires a membership they can't get.
Name each deletion in the output (e.g. "dropped: paid practitioner community - no budget"). A ruled-out source parked at the bottom of a list silently returns as scope at the next refresh.
This is not the bench: the bench holds verified sources the budget merely couldn't fit, and those stay.
4. Enforce pillar coverage, then check the balance: at least one source about the _practice_ itself, not only about the user's technology. An ecosystem-only radar makes a strong engineer and a weak advocate.
5. Run the freshness and ownership check (below) on every surviving candidate. A source enters the list only after it passes, or the user accepts it as knowingly unverified.
6. Cost each candidate as an order of magnitude of attention, never a precise figure:
- Newsletter issue or blog skim: minutes.
- Conference-talk video: tens of minutes.
- Peer community: tens of minutes to skim, hours if they post rather than read.
- Podcast episode: most of an hour.
- Annual ecosystem survey or community-health report: one concentrated read a year.
- Conference: days in one block, plus travel.
Halve any audio that rides on time already spent - commute, exercise - because that is not attention the user has to find.
7. Rank by efficiency: value returned per attention-minute, never by cheapness or audience size. State value as the outcome bought, never as an adjective. The axes disagree; read all three:
- effort (attention per week): `podcasts > community participation > video > newsletter == blog skim > annual data report` - conferences sit off this line.
- value (what it buys): `community == conferences > podcasts > annual data report > newsletters == blogs > video`
- efficiency (the default order): `annual data report > newsletters == blogs > community skim > podcasts > video`
Why each rung lands where it does:
- **Annual data report tops efficiency**: one concentrated read a year buys the citable number every DevRel budget and headcount conversation runs on - the one place in this field where the cheapest option and the most efficient one genuinely coincide, and it still is not the most valuable.
- **`newsletters == blogs`**: a real tie on both axes - same skim cost, same good, what happened, in text quotable in a planning doc. Break it by pillar fit, never by which is better known.
- **`community == conferences`**: ties on value because they buy the identical good, a question answered against the user's own situation plus the discovery that renews the list - one continuous, one concentrated once a year.
- **Conferences sit off the efficiency line deliberately**: amortising three days across 52 weeks makes them look nearly free and ranks them first, which is arithmetic lying about a cost the user pays as cleared days and travel.
- **Evergreen reference works** (a docs framework, a maintainer handbook) sit outside the weekly budget entirely rather than being ranked in it: they are a one-time read, and giving them a per-week ratio would be false precision.
Within a medium: `pillar fit > role fit > durability`. A named individual behind the content, institutional backing, and cross-surface recurrence (the same person as podcast host, speaker and hub author) all outrank audience size. Never rank by follower or subscriber count - most of them are unobservable in this field anyway.
8. Name what this order starves. Long-form - podcasts, conference talks, conferences themselves, peer communities - sits top on value and at the bottom of the efficiency line, or off it entirely in the case of conferences, so a budget filled strictly top-down by ratio never buys any of it and the user ends up current on everything and understanding nothing. Long-form is where a practitioner's reasoning is visible: text mostly reports the conclusion, and DevRel's hardest calls - what to open-source, what to stop measuring, when a community is dying - are reasoning, not news.
Promote it anyway when any of these hold:
- The user is new to DevRel, or has just changed ecosystem, pillar or seniority, and lacks judgment rather than headlines.
- They answered "catching up" (Q4a) rather than standing habit.
- They are submitting talks, sponsoring or hosting (Q9b/c), which makes conferences the work rather than a reading cost.
- The audio rides on commute or gym time, which removes the cost that lost it the round.
The reserved community slot in step 9 is the standing floor for this - a floor, not a reward for winning the ratio.
9. Fill the budget. Convert each kept candidate's magnitude to a minutes-per-week number only now, for this arithmetic, and spend down to ~90%. Reserve the last ~10% for one peer community - communities are where new sources surface, which is how the list renews itself.
Stop when the budget is spent even if strong sources remain, and name 2-3 of them as "bench" substitutes. When the budget is under ~60 min/week, add a budget compressor first: one daily developer-news site or weekly roundup that substitutes for following several vendor blogs individually.
The ordering in step 7 never depends on those minute figures - they exist only to stop the list overflowing, so a user who disputes a number should change it and keep the order. (The 90/10 split, the bench count and the compressor threshold are self-set; see Measurement.)
10. Re-rank against what you already know about this user, and say which fact moved which source:
- A newsletter, report or community their employer already pays for costs nothing extra to add, so its price stops being a reason to skip it.
- A conference budget turns an event from a personal expense into a cleared slot.
- A colleague already inside a gated community can be asked instead of joined.
- Speaking at or sponsoring an event changes what it returns, not just what it costs.
The order is a default, not a law: it is calibrated for a time-poor practitioner who reads, and it shifts with the interview and with who executes it. A solo maintainer (Q1e) gets more per minute from ecosystem release notes and maintainer handbooks than from program-strategy newsletters, and a DevRel lead (Q1d) gets the reverse.
11. Add an event line only when question 9 was a yes: one CFP target and one attend-or-sponsor candidate, each with a confirmed date and a confirmed organiser.
12. Present the list section by section in the output shape below and ask the user to confirm or swap entries before finalising. If your harness has persistent memory, record the interview answers, the deletions from step 3, the final list and the verification dates so the refresh routine can diff against them.
## Freshness and ownership check
Verify before recommending. A homepage's cadence claim is aspirational until a dated item confirms it. If you can browse or fetch the web, for each source:
1. Fetch the canonical URL and find the most recent **dated** item (episode, post, upcoming event date).
2. Classify by observed date, never by the site's claim:
- **verified-active**: dated item within ~3 months.
- **verified-stale**: reachable, newest dated item older than ~6 months - keep only if the user accepts it.
- **dead**: parked, for-sale, or resolving to an unrelated business - hard-remove.
- **unverified**: fetch failed, or the page renders no dates (record the reason). An HTTP 403, 5xx or consent wall is _unverified_, never _dead_.
3. **Check who runs it, not only when it last published.** Conferences change organisers, vendors get acquired, agencies wind down. When the owner changed, keep the source, record the new owner, and re-read what it now covers - an acquired vendor's blog often keeps its cadence and loses its DevRel angle.
4. Prefer podcast feeds to marketing homepages for dates. Several shows expose no dates on their own site while the feed gives an exact one; one show's homepage blocks automated fetching entirely while its feed answers instantly.
5. Treat evergreen reference works differently from feeds. A practice hub's guides, a docs framework and a maintainer handbook legitimately carry no dates - judge them on maintenance signals (a live event listing, a current copyright, an active repository) and label them "evergreen, undated" rather than forcing a staleness verdict.
6. Treat gated communities as unobservable from outside. Record membership figures as claimed-not-verified and check the join flow works instead.
7. **Treat a URL as evidence about the URL, never about the entity behind it.** Three instances:
- A parked or for-sale personal domain makes the person _unverified_, never inactive - an agency founder's personal domain can sit on a for-sale page while his company publishes weekly. Track the person through a surface they actually publish on: a podcast feed, an employer page, a speaker roster, a hub byline.
- A URL that resolves can still have changed hands - the most damaging failure in this field was a remembered brand domain that now redirects to an unrelated business. Confirm the destination's content, not just that the URL resolves.
- NXDOMAIN on a guessed domain is evidence about the guess. Before writing an organisation off, search the code host for its name, read its declared website field instead of guessing, sort its repositories by last push, and read the repo _descriptions_ - deprecation gets declared there first. The field's own foundation is findable exactly this way, through its code-host organisation rather than a remembered domain; commit timestamps also beat homepages that render only a "Loading…" placeholder to a fetcher.
The freshness windows above (~3 months active, ~6 months stale) are a self-set baseline, not an industry standard. Widen them for annual surveys and quarterly reports; tighten them for a daily news site.
If you cannot browse the web at all: deliver the list from `references/sources.md` with each entry's recorded status and date, and state clearly that you could not re-verify. Hand the user the manual check:
- Open each URL.
- Find the newest dated item.
- Confirm the owner.
- Apply the classifications above.
## Periodic refresh routine
If your harness supports scheduled routines, install a quarterly refresh - quarterly is this skill's own default cadence, not a published standard. Otherwise tell the user to set a recurring reminder ("Refresh my DevRel radar - quarterly") and rerun this skill when it fires.
1. Re-ask which pillars the user owns - DevRel scopes shift with headcount, and a new pillar voids the coverage guarantee until a source covers it.
2. Re-resolve every URL, including the ones that worked last time, to catch renames, acquisitions and resold domains.
3. Re-run the freshness and ownership check; downgrade newly stale entries, remove dead ones, retry previously unverified ones.
4. Ask which sources the user actually consumed last quarter and drop the ignored ones - an unread source costs attention anyway. Never re-offer a source deleted for a constraint unless the user says the constraint has lifted, and re-run step 10's re-rank: a new employer subscription or conference budget changes the ratio without changing the source.
5. Refresh the event calendar twice a year rather than quarterly - CFP deadlines land months before the event, so a stale calendar costs a speaking slot, not just a reading slot.
6. Ask the peer community and the newest additions for one candidate discovery each; verify before promoting it to the bench or the list.
7. Re-total estimated weekly minutes against the budget and trim the overflow.
## Output shape
Deliver one watch-list artifact. Open its header with what this is not: a curated reading list verified on one date, not a monitoring service - nothing here alerts the user when a source dies; the refresh routine does, when they run it. Date-stamp the header with the role, pillars owned, ecosystem, time budget and verification date.
Group by consumption rhythm:
- **Weekly core**
- **Monthly**
- **Annual** (data and events)
- **Bench** (verified substitutes)
Per entry, include:
- Name
- URL
- Medium
- Pillar(s) covered
- Estimated minutes
- One line on why it earned the slot
- What they're selling
- Status + date
Order the entries inside each section by efficiency, highest ratio first, and say so in the header rather than leaving it implied by row order.
Close with totals:
- Estimated weekly minutes vs. budget.
- Counts per section.
- Verified-active count.
- An explicit pillar-coverage line ("every owned pillar has a verified-active source: yes/no").
- A **Dropped** line naming every source deleted for a constraint, with the constraint that deleted it.
See `references/watch-list-example.md` for a worked example and a negative example.
Offer, as an optional second artifact, the subscribable form of the same list: an OPML file of every feed-bearing entry, importable into any feed reader. A watch list the user has to re-type into a reader gets read once.
Invocation examples:
- "Build me a DevRel radar - solo advocate at an API company, about an hour a week."
- "Which DevRel podcasts and newsletters are actually still active?"
- "I run docs and community for a Kubernetes tool. What should I read, and which conferences should I submit to?"
- "Refresh the DevRel radar you built me last quarter."
- "Who should I be following in developer relations, and what are they selling?"
## Failure modes
- **Inventing a source.** DevRel's canon is small, so a plausible-sounding show or newsletter that doesn't exist is easy to produce and instantly destroys trust in the rest of the list. Every entry traces to a fetched page or is labelled unverified.
- **Passing a URL verdict off as an entity verdict.** A resold domain that still resolves, a parked personal page, an NXDOMAIN on a guessed domain - all one mistake, covered by check 7 of the freshness and ownership check. Re-run it rather than reasoning from the URL.
- **Right date, wrong owner.** A conference whose organiser changed passes any freshness check while the attribution is wrong. Check both.
- **Forcing a staleness verdict on an evergreen reference.** A framework or maintainer handbook has no cadence to be stale against.
- **Quoting a benchmark without its edition and date.** Ecosystem surveys are annual; a bare statistic ages invisibly and gets repeated in a leadership deck.
- **An ecosystem-only list.** Following only your technology's sources leaves the practice itself unlearned.
- **Filtering out everyone with something to sell.** That empties this field's list; disclose the incentive per entry instead.
- **Over-stuffing past the budget.** Cut to fit and use the bench.
- **A flat list.** Twelve equal-looking sources get picked by taste, or by whichever sits first. Order by value per attention-minute and say the ordering out loud.
- **Ranking by cheapness.** Cheap and efficient are different orderings, and only the second one answers "what do I read first". A five-minute newsletter that buys five minutes of headlines is a rounding error, not a quick win.
- **A budget filled purely by ratio.** It buys no podcasts, no talks, no conferences and no community - everything long-form loses every round - and leaves the user current on everything and understanding nothing. Check step 8's promotion conditions before finalising.
- **Amortising a conference across 52 weeks.** That arithmetic ranks a three-day trip above a newsletter. The user pays it as cleared days, so it stays off the efficiency line.
- **Demoting a ruled-out source instead of deleting it.** A paid community the user can't expense, parked at the bottom, reappears as scope at the next refresh. Delete it and name the deletion.
- **Pricing attention in money.** The axis is the user's attention and cleared days. A source their employer already pays for costs them nothing extra - that belongs in the step 10 re-rank, not in the ranking itself.
## Measurement
At delivery, the pass bar is:
1. Every pillar the user owns has at least one verified-active source, and no pillar they don't own is padded in - absolute.
2. Total estimated weekly minutes at or under the budget - the budget is the user's; the per-medium magnitudes behind the total are this skill's self-set defaults, and the minutes exist only for this arithmetic.
3. Every entry carries a what-they're-selling flag and a status + date - absolute.
4. Every entry traces to a fetched page or is explicitly labelled unverified with its reason - absolute; zero invented sources, zero unverified entries presented as verified.
5. Every section is ordered by value per attention-minute, the ordering is stated rather than implied, and every re-rank away from the default names the fact that moved it.
6. Every source the user's constraints ruled out was deleted and named as dropped, not parked at the bottom - and the list is not long-form-free: if it contains no podcast, talk, community or conference, step 8's promotion conditions were checked and the reason for skipping them is stated.
At each quarterly refresh, additionally check that the user consumed at least two-thirds of the entries and that no listed source changed owner without the entry being updated. If any check fails, revise - re-verify, trim, or swap from the bench - and re-present until all pass.
These numeric baselines are all self-set, chosen because a list the user does not finish is a list they will abandon:
- The ~60-minute compressor threshold.
- The per-medium minute conversions.
- The ~90/10 split and 2-3-entry bench.
- The two-thirds consumption rate.
- The quarterly cadence.
Move them if the user's own consumption data disagrees. Moving them never moves the ordering: the ranking is built on orders of magnitude, and the minutes only decide where the list stops.
## References
- [./references/sources.md](./references/sources.md) - the categorised, date-stamped source list (practice hubs, podcasts, newsletters and media, communities, events, data and benchmarks), plus the entries rejected as dead or resold.
- [./references/people-to-follow.md](./references/people-to-follow.md) - practitioners with their verifying surface, selling flag and cross-surface recurrence.
- [./references/watch-list-example.md](./references/watch-list-example.md) - one worked watch list and a negative example.
- See samber/developer-relations-skills@developer-relations-kickoff to route a task across this collection.
- See samber/developer-relations-skills@devrel-career for landing and growing a DevRel role; this skill only curates what to read, watch and attend.
- See samber/developer-relations-skills@devrel-metrics when the data sources here get used to build a measurement framework.
- See also samber/dev-event-organizer-skills for running an event, once the calendar here identifies one worth hosting.