Aurornis
an hour ago
I wish this person the best of luck in their next role.
I've known some great DevRel people, but it's a difficult role. The company can frequently have very different ideas about what DevRel should look like than the person hired into the role. The best DevRel people I know spent their time doing things to fill in gaps left by the company such as providing better documentation, example repos, and filtering through all of the noisy chat across Discords and subreddits to get additional feedback into the company. For the right person it can be fun, but playing cleanup crew and trying to keep customers happy by patching all the holes left by other teams gets old.
I don't know this person specifically, but from the way they write it's obvious that they like doing Twitch streams, podcasts, and workshops, but they don't like doing it for a company:
> After all these years I can finally say out loud: I do not want to be the face of a company. I do not want to speak at conferences or on podcasts or do workshops in order to try and sell you a product. I do not want my value determined by arbitrary gamified metrics like how many video views or blog post views or company sign-ups I generate in a landscape that is completely out of my control. I do not want to be perceived. For being perceived is breaking me, and I need to put myself back together.
This paragraph is basically "I hate DevRel work".
Unfortunately, doing those things for a company is the point of the job. If they hated this, then burnout was inevitable. Streaming to a couple hundred people on Twitch and traveling the world for workshops and getting paid for it sounds fun to a lot of people pursuing DevRel, but the part about looping it back to a company's best interests has to be at the core of it.
danabramov
an hour ago
In practice, "what's actually best for the community" (growing a community of engaged engineers who feel listened to and who understand what you're doing) is not necessarily easy to show by metrics. I think the author is making a subtler point that, even if you don't hate DevRel work, the most useful kind of work is often unappreciated or devalued by decision makers.
Aurornis
an hour ago
True, but in practice "the community" as the DevRel person sees it can be very different than the customer base that the company wants to address.
For example, this DevRel person talks a lot about their Twitch stream and all of the work they put into a game on it that also used Sentry (their DevRel employer). It's all very cool and impressive work, but for a company like Sentry with 100,000+ customers there are millions of engineers across those companies that make up their developer base. Streaming to a couple hundred people on Twitch doesn't even register as interacting with the community.
Reading some of the linked posts there's an ongoing frustration with being asked to provide metrics and prove value, which gets to the core of what I was trying to say above: What some people want to do for DevRel for a small audience (Twitch streaming, podcasts, workshops) is often at odds with what the company expects them to do for their large base of active developers and users.