There are two types of developer relations (DevRel as you call it): Technical support and informational blogging.
For the first type, GitHub issues is a good place to go for developer relations.
Discord chat is another place. You can easily turn a Discord server into a support portal or even a call center style system (i.e. auto-kicks people who leave the server so that those who show up get direct 1:1 support and doesn't devolve rapidly into politics).
Good tech support developer relations can also be done via email. As long as you respond positively and within a reasonable timeframe, most people will respect that.
Twitter has always seemed like the wrong place to have real conversations with devs about technical issues outside of emergency situations (i.e. all other contact methods have broken down). Limited character lengths means longer posts will take a lot longer to digest and respond to.
For informational blogging such as writing in-depth technical articles that will be indexed by search engines, there are plenty of options from places like dev.to, Blogger, WordPress, etc or a self-hosted blog. There's also the option to publish content in other formats such as podcasts or video which can work...but sometimes text on a page is best. For example, I don't think a podcast would work all that well when attempting to disseminate a few pages of code, "Line 10. x = y * 2; Line 11. ..."
Brian Rinaldi is a Developer Experience Engineer at LaunchDarkly with over 20 years experience as a developer for the web. Brian is active in the community running CFE.dev and Orlando Devs.
Thank for the comment. I don't think technical support is typically classified as developer relations. DevRel is about developers developer outreach with the goal of "authentically" marketing to and selling to developers (though there's a second aspect of bringing the perspectives of the developer community back to the company). Technical support and support related content isn't the same. For example, a podcast works well for DevRel because it's about outreach, but not well for support because, as you note, it's not the best place to discuss specific code examples.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are two types of developer relations (DevRel as you call it): Technical support and informational blogging.
For the first type, GitHub issues is a good place to go for developer relations.
Discord chat is another place. You can easily turn a Discord server into a support portal or even a call center style system (i.e. auto-kicks people who leave the server so that those who show up get direct 1:1 support and doesn't devolve rapidly into politics).
Good tech support developer relations can also be done via email. As long as you respond positively and within a reasonable timeframe, most people will respect that.
Twitter has always seemed like the wrong place to have real conversations with devs about technical issues outside of emergency situations (i.e. all other contact methods have broken down). Limited character lengths means longer posts will take a lot longer to digest and respond to.
For informational blogging such as writing in-depth technical articles that will be indexed by search engines, there are plenty of options from places like dev.to, Blogger, WordPress, etc or a self-hosted blog. There's also the option to publish content in other formats such as podcasts or video which can work...but sometimes text on a page is best. For example, I don't think a podcast would work all that well when attempting to disseminate a few pages of code, "Line 10. x = y * 2; Line 11. ..."
Thank for the comment. I don't think technical support is typically classified as developer relations. DevRel is about developers developer outreach with the goal of "authentically" marketing to and selling to developers (though there's a second aspect of bringing the perspectives of the developer community back to the company). Technical support and support related content isn't the same. For example, a podcast works well for DevRel because it's about outreach, but not well for support because, as you note, it's not the best place to discuss specific code examples.