Newsletter
Measuring our work is important. Let’s face it: not every company gets the role of Developer Relations. I’m not going to belabor the point, but in lean times demonstrating your value to the organization has merit. At the same time, measuring what matters gives you room to experiment,
Newsletter
I organize Developer Advocacy around four specific areas. That’s not to say that any individual does or does not do all four. It’s more that our roles can be boiled down to these core areas. 1. Capture and represent product feedback 2. Build credible and authentic content that
Newsletter
I spoke with someone recently who didn't know where to start with their first hire in Developer Relations. As folks who know me appreciate, I think of the Developer Relations organization as the following distinct functional areas: * Developer Advocates: they're the spine of your Developer Relations