Developer relations is an integral part of many software companies that hope to win the hearts and minds of developers. You may refer to it as developer evangelism or community outreach but ultimately, it’s a motion dedicated to ensuring that you’re proactively listening to what the community needs and looking to see how you can help, providing a conduit for developers to offer you feedback and have an opportunity to share your vision with the community and hopefully solve some of their problems. In my opinion, this is absolutely the right order to be driving on since it’s important to always think of the needs of the community. But the problem with developer relations is that it’s a subjective, somewhat nebulous field that in most cases doesn’t involve tangible “things“. This can make it hard to measure how successful you or your team are and if you’re hitting the mark with your community. What do Developer Advocates do? From my experience and through many discussions with my peers, the typical developer advocate tends to focus on several key outreach mechanisms to engage with developers. These are: Social media engagement, primarily Twitter Content generation via blogs or 3rd party sites such […]
WebDev: How to Use NGROK to Test a Local Site for Microsoft Edge and…
Manifold.JS: How to Build a Hosted Web App on Android, iOS, and…
Are You Ready for the Ultimate Online P2H Easter Egg Hunt?
Essential: How to Test Internet Explorer on Android, iOS, and Mac OS X
Social Media Marketing: Finding Influencers to Support Your Brand
JavaScript: Using Closure Space to Create Real Private Members