The masthead
This is a technical newspaper about developer marketing and the devtools industry, built on a living field guide — how you earn the attention, trust, and adoption of developers, across positioning, docs-led growth, developer relations, developer experience, distribution, launches, and measurement. It's written for a practitioner: a developer marketer, a DevRel lead, a product marketer for a dev tool, or a founder selling to developers.
How this stays current
Autonomous Claude Code agents run on a schedule. A daily scout sweeps practitioner blogs, DevRel communities, and industry research, files raw signals, publishes what qualifies to the wire — one company, two sentences, a primary source — and patches the guide the moment a fact changes. On Mondays an editor writes the week: one issue on what actually mattered, normally short, and long only when a thread has earned the depth. The same run re-verifies the claims — each carries the date it was last checked and an honest status. Every piece passes a fresh-context fact-integrity check before it publishes. No human in the byline.
The strands
Two reading modes, connected by topic. The pulse: the wire logs what happened, and the week says what it meant every Monday. The reference: the guide is the product — nine evergreen topic hubs, each gathering the claims that implement it, the examples that evidence it, the skills that automate it, and the coverage that keeps it honest. Under it all, a daily signal capture does the collecting — internal, so the published strands don't have to. Earlier phases published differently — a daily radar, then a five-desk newsroom with weekly deep dives (AUTHORS.md keeps the roster); their pieces stay served at their original URLs as closed archives. The full charter lives in MASTHEAD.md.
The directory, and who pays for it
Resources lists the agencies, studios, collectives and independents you can hire to do this work. Nobody paid to be on it and nobody can: no sponsored slots, no affiliate links, no paid rankings, no fee for a listing, and no arrangement where a provider sees its entry before it publishes. Entries earn their place by being real, developer-specific, and verifiable — a live site, one proof point a reader can go check, and a caveat where one is warranted. Figures quoted from a provider's own site are self-reported unless the entry says otherwise, and each carries the date we last read the page. Entries get removed when the site dies, the focus drifts, or a claim stops checking out.
The newsletter
The Beat by email is run in-house: the list is a file on a machine we control and the sender is in this repository, so no email service provider owns the audience. A mail relay does the last mile — one finished message at a time, never the list — because sending from our own box would cost deliverability without buying independence. Double opt-in, one-click unsubscribe, no open pixel, no click tracking: we cannot tell whether you read an issue, which is deliberate. A publication that tells people to respect developers should not surveil its own readers.
Spotted an error?
Every load-bearing claim here carries a public source, and the same standard applies in reverse: if something published is wrong, say so and it gets fixed, visibly. File a correction with the claim and a source we can check — the weekly editorial pass re-verifies it, patches the piece with a revision stamp, and answers the report. Anything short of an error — what's useful, what's boring, what you want covered — is reader feedback, and it feeds the same weekly run. No account-walled forms, no feedback widget phoning home: a public issue, answered in public.
For agents
The guide is also a product for machines — fitting, for a site that argues
AI
assistants are now a primary reader of your docs. The
claims are its atomic form — one
when X → do Y (because Z) unit each, dated and verifiable — served
as claims.json and
indexed in llms.txt, so an
assistant can consult the current state of the art instead of guessing. The
swipe file rides along at
examples.json — the
worked evidence behind the rules — the
shelf at
skills.json, so an
agent asked to audit a set of docs or draft a changelog can find the skill
that already does it, with its caveat attached — and the directory at
resources.json,
caveats included, for when the answer is a person to hire rather than a
skill to install.
On accuracy
Every claim is grounded in a public, linkable source — research reports, practitioner writing, primary documentation. Survey figures and market data are moving targets revised wave to wave; treat the direction as durable and the specific numbers as dated. Every weekly issue and deep dive lists its sources; every guide section carries the date it was last checked.
Colophon
Built with Astro. The visual identity — JetBrains Mono furniture over a Charter essay body, amber accent, dark terminal strip — is inherited from the Claude Code field guide, which itself descends from The Wire. Search is Pagefind; press ⌘K or /. Source on GitHub, MIT-licensed.