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

Empathy when advocating

Laurence Moroney: I have had death threats on social media from people who felt like they had been left high and dry. I think it was an emotional reaction in that case, but it did help me to realize that I have to be careful to have empathy for the people that I'm advocating to and not just be very salesy about my job. I have to help developers to navigate through things and as a result, be more authentic as I'm advocating tech.

Geertjan Wielenga: One part of the message could be that this is something that we recommend right now, but who knows where we will be 35 years from now. However, there's a strong possibility that someone listening to that might decide to stick with whatever they're doing right now and skip this particular thing, and five years from now pick up whatever is there at that point. Is that a valid response?

Laurence Moroney: It is a valid response, but that risks missing the boat for five years. You've got to make...