Practical, field-tested tactics from a DevRel leader who leaned into high-velocity content, public engineering, and unconventional community moves while working at GitHub, TBD (Block), and Block Open Source.
Operate hands-on: build publicly, ship code, and keep docs current so leadership sets an execution standard rather than only dictating volume.
Prioritize high-velocity, good-enough content over quarter-long perfection cycles to remain relevant in a rapidly shifting AI landscape.
Use low-pressure, entertaining formats (e.g., competitions, chaotic demos) to reduce friction for live demos and broaden audience access.
Developer Relations (DevRel) feels stuck. As companies pivot to AI, marketing moves look similar and developers are overwhelmed by choices. The author frames the modern DevRel operating model as broken because teams struggle to stand out and deliver measurable impact.
Tactical playbook for DevRel leaders
Continue to build and ship. The author maintained three specific habits: publish step-by-step public builds, contribute code to the agent repo to fix real issues, and continuously maintain documentation because docs are the product's front door.
2) Meet developers where they are in real time
Base content (installation guides, walkthroughs) is necessary but insufficient. The team must inject the product into live ecosystem conversations. One example: when "Ralph Loops" trended on social platforms, the author jumped on a livestream to build it, then converted the stream into a polished video and a written tutorial explaining how to reproduce the setup with goose.
4) Lower friction for live demos with playful formats
Early-generation AI models made live demos risky. The author introduced a short, snappy competition—The Great Goose Off—where participants built chaotic, entertaining tools. That format made failures enjoyable, reduced pressure on contestants, and increased viewer engagement.
5) Use transparency and external collaboration to build trust
How these moves connect to measurable impact
The tactics repeatedly link back to concrete outcomes: high-demand talks that enterprises redistributed, wider discovery by moving content out of private channels, code contributions that reduced product friction, and formats that kept audience attention even when models underperformed. Each move trades polished perfection for broader reach and discoverability.
Practical next steps for DevRel leaders
These tactics prioritize presence, speed, and developer empathy over playbook-safe marketing that blends into the crowded AI ecosystem.
The DevOps community has already experienced technological extremes. You might recall the time when automation was thought of as a panacea for all possible engineering issues, and the slogan “Automate Everything” was ringing out everywhere. Over time, the industry came to an important conclusion: Automation should not
How do you know when an AI use case is too risky to pursue? The answer has less to do with the technology itself and more to do with whether your organization has the governance, processes, and decision-making discipline needed to support it.
Safety is the watchword, but there could be ulterior benefits for the industry.
A startup changes the model behind its AI feature. The new model is faster, cheaper and performs better on public benchmarks. The engineering team runs its tests, deploys the update and waits for the improvement. Instead, support tickets begin to arrive. The assistant is less accurate on short questions. It misundersta
Debian’s new AI contribution policy avoids bans and mandatory disclosure, instead making developers responsible for reviewing AI-generated work and protecting sensitive data.
Tratando de ser un desarrollador AI First sin vender humo Joel Humberto Gómez Paredes Joel Humberto Gómez Paredes ...
Loading more related stories...
Open the app view to save this story, compare related coverage, and continue from the same source.