Book Image

Developer, Advocate!

By : Geertjan Wielenga
Book Image

Developer, Advocate!

By: Geertjan Wielenga

Overview of this book

What exactly is a developer advocate, and how do they connect developers and companies around the world? Why is the area of developer relations set to explode? Can anybody with a passion for tech become a developer advocate? What are the keys to success on a global scale? How does a developer advocate maintain authenticity when balancing the needs of their company and their tech community? What are the hot topics in areas including Java, JavaScript, "tech for good," artificial intelligence, blockchain, the cloud, and open source? These are just a few of the questions addressed by developer advocate and author Geertjan Wielenga in Developer, Advocate!. 32 of the industry's most prominent developer advocates, from companies including Oracle, Microsoft, Google, and Amazon, open up about what it's like to turn a lifelong passion for knowledge sharing about tech into a rewarding career. These advocates run the gamut from working at large software vendors to small start-ups, along with independent developer advocates who work within organizations or for themselves. In Developer, Advocate!, readers will see how developer advocates are actively changing the world, not only for developers, but for individuals and companies navigating the fast-changing tech landscape. More importantly, Developer, Advocate! serves as a rallying cry to inspire and motivate tech enthusiasts and burgeoning developer advocates to get started and take their first steps within their tech community.
Table of Contents (36 chapters)
34
Other Books You May Enjoy
35
Index
36
Packt

Proving your worth

Geertjan Wielenga: This is the standard problem. How do you prove to upper management that you're not a cost center or that the cost center is justified?

Patrick McFadin: I've talked about this at conferences before. The pitfall in developer relations is that we get sucked into the same kind of measurement statistics that marketing does. We start to focus on qualified leads and key performance indicators (KPIs). We start trying to calculate how many people we've talked to. That's the wrong approach; we already have a marketing department for that.

Developer relations is about awareness and the developer experience. How do you measure that? It's very difficult convincing a business that you should be measured much more like an engineering team and much less like a marketing team. What's the return on investment (ROI) on a developer building code? Give me the metrics that show the ROI. They don't exist. We hire developers to work toward an...