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

Developer advocacy's recent growth

Geertjan Wielenga: It seems to me that very few people know about this profession. Do you agree with me?

Andres Almiray: I definitely agree with you. I think that we have seen, in the past few years, more and more tech people jump into the option of traveling around the world, which involves letting potential customers and developers know what's happening in their particular neck of the woods and what they're doing in a particular niche.

I believe that this change is because companies have figured out that if you don't reach out to developers directly, then it's much harder to sell particular solutions. It doesn't matter how easily you can convince the decision-maker, or the people at the top of the chain, if once they push down a particular solution the developers won't accept it. You have to find a way to convince both the people at the top and the developers. You have to find a way to do it properly too.

Geertjan Wielenga...