Kind of an odd take. The first folks performing what we now call DevRel were engineers, founders, VPs, and directors. Even now a vast majority of DevRel practitioners are engineers. Which means they do more than one job.
As far as being disrespected or viewed as divas, it's ironically engineers that meme-ify DevRel folks.
As far as the three points, much like every engineer that writes a post about the pointlessness of code tests in the interview process, sometimes things don't change. Granted, those three points haven't been made in "every single devRel blogpost you read since 2012" since the term DevRel was really coined in 2014-ish. but that's not really the issue.
No, there are still many things unresolved in the DevRel industry. It's much bigger than it was, yet "pure engineers" slough it off as meme-worthy and management still can't see past it being marketing or pre-sales. So more people add their voice in an attempt to improve things.
You don't stop saying something needs to be fixed just because it's been said before. You keep saying it until it's fixed.
Full disclosure: I work at Humio. Great, cost-efficient monitoring, sub-second ingest latency, on-prem or in the cloud. Feel free to check it out - humio.com
I can vouch for it - it's solid. Feel free to jump into #engineyard on IRCFreenode if you have any questions - or just use the trial hours to spin up a staging version and give it a try.
Dude - I can't believe they held your family and wouldn't let you leave! I was shocked at the way they treated Zak and I when we left, but never expected anything of this magnitude.
At least you pulled off an amazing conf despite all the following bullshit.
We are pretty open about what we are up to