In “Developer Relations: A Painful Reckoning“, I laid out the current broken state of developer relations and it got people fired up. Some

In a Post Developer Relations World: Fix or Fire?

submited by
Style Pass
2024-11-18 16:00:04

In “Developer Relations: A Painful Reckoning“, I laid out the current broken state of developer relations and it got people fired up. Some people called me an “instigator” (fact check: true), others a “doomer” (okay but not productive), some that I was wrong (without feedback), and a few offered a thoughtful counter. Luckily, for everyone who put their fingers in their ears shouting “nuh uh!”, twice as many asked:

To those people: Thank you. Now that we agree on the problem, let’s explore some fixes. It’d be nice if there was a single, clear cut answer, it depends on your organization, your goals, and the people you have. Before we try to define what DevRel should be, let’s lay out our options and what it’s not.

Unfortunately, firing DevRel appears to be the most common approach at the moment. On the surface, it makes sense. They’re expensive and since there are fewer events, one of their single biggest value props is gone. If you just want someone to write some blog posts and creative tutorials, there are cheaper ways and – if you hire people from your target markets, frameworks, etc – you can probably get audience and distribution in the deal.

Leave a Comment