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

Personal qualities needed

Baruch Sadogursky: I'm constantly recruiting because the right kind of people for these roles are hard to find. Most of the functions in developer relations are technical.

There are obviously some roles that are not technical, such as a community engagement manager or a community builder, but developer advocates, engineers, and technical writers all have to be technical.

The other side of this role is that you need to be an outspoken and community-loving person. I used to say that people in developer relations need to be extroverts until I was corrected; I was told that many people who do these roles are not actually 100% extroverted. They don't necessarily get energy from other people, but they still know how to engage. I'm more cautious now when I talk about requirements in developer relations, although I think that it is easier for extroverts, who naturally get their energy from engaging with other people.

Geertjan Wielenga: Why is the...