Developer Advocate here (who works in Developer Relations). I think "DevRel" is a big bucket, but what the author is calling "Developer Relations" is just the most visible subset of the bucket.
The impression is that a "DevRel" spends all their time writing talks, traveling to conferences, pitching products and speaking. This makes sense, because the "DevRels" you probably see the most are the ones that are doing these things, and you don't see them doing anything else. A lot of people are surprised to discover that traveling and speaking is actually a very small part of my job, given the number of talks I give, and how often they see me at events.
I think part of this perception comes from the conflation between an advocate and an evangelist. There is endless debate about what these terms mean in the context of developer relations, but for me, the difference is this:
* Evangelists want users to know that a product exists: They're speaking to developers, about the product. They probably report to & work with Sales/Marketing.
* Advocates want products to know that their users exist. They're speaking to product owners, about the developers. They probably report to & work with Engineering/Product.
Both roles are equally important (and sometimes done by the same person), and the "publicly-validated credibility" the author talks about is just as valuable to the product team as it is to the sales team.
I'd add that there's often a community management aspect to the role as well and sometimes that's the title. In general, I find a lot of different titles used which may or may not reflect what the person does day to day.
I even know people who are also product managers who do a fair bit of outward-facing DevRel/Evangelism type of work.
And skill sets vary quite a bit too. I know folks who do a ton of coding, creating demos, etc. And I know others who, while typically at least somewhat technical, are much more on the relationship and community-building side of things.
The impression is that a "DevRel" spends all their time writing talks, traveling to conferences, pitching products and speaking. This makes sense, because the "DevRels" you probably see the most are the ones that are doing these things, and you don't see them doing anything else. A lot of people are surprised to discover that traveling and speaking is actually a very small part of my job, given the number of talks I give, and how often they see me at events.
I think part of this perception comes from the conflation between an advocate and an evangelist. There is endless debate about what these terms mean in the context of developer relations, but for me, the difference is this:
* Evangelists want users to know that a product exists: They're speaking to developers, about the product. They probably report to & work with Sales/Marketing.
* Advocates want products to know that their users exist. They're speaking to product owners, about the developers. They probably report to & work with Engineering/Product.
Both roles are equally important (and sometimes done by the same person), and the "publicly-validated credibility" the author talks about is just as valuable to the product team as it is to the sales team.