Developer Experience

Developer Experience (DX) should be the central focus of any DevRel strategy, as it is both the prerequisite for success and the primary outcome of the team's work. This view positions DX as the core value a developer experiences, with other activities like education and marketing contributing to it.

Framing Developer Relations solely as a form of developer marketing is an incomplete and damaging view that leads to focusing only on outward promotion. DevRel is better understood as a process of value co-creation that includes a critical internal feedback loop to influence the product roadmap.

DevRel teams often fail to prove their value because they measure activities and outputs like blog posts instead of the business outcomes they influence, such as product adoption. To succeed, DevRel must define and relentlessly communicate its impact on business value.

The traditional DevRel model of creating tutorials and documentation is now obsolete, as AI agents can handle boilerplate code, explain APIs, and debug integrations. DevRel's value must shift from creating content for humans to provisioning context for AI systems and acting as auditors for AI-generated code.

The rise of AI agents means DevRel's focus must shift from creating human-facing tutorials to provisioning machine-readable context so that LLMs can use the product effectively. In this new model, the AI agent is a first-class developer persona and DevRel's role becomes ensuring systems are "model-ready."

The idea that DevRel is shifting into a developer go-to-market (GTM) function is incorrect because it has always served this purpose, connecting activities like content and community directly to business goals. The only recent change is that economic pressures have reduced leadership's patience for seeing revenue-related results from DevRel.

Advocate originally meant a senior engineer acting as Customer Zero who took the world to the product; commoditisation turned it into a charismatic lead-gen role and left a vacuum where technical authority used to be.

There is no one-size-fits-all strategy for DevRel, and teams that simply copy the playbook of another successful organization are likely to fail. A DevRel strategy must be tailored to the specific company's context, including its lifecycle stage, business model, and the technology cycles it operates within.