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

Criticizing competitors

Josh Long: I'd say that's more a marketing function. All of us are given to being snarky, especially these days. It's so easy to be critical about competitors, or take pot shots, but if you do that, you're not the best advocate.

I'm not trying to diminish other techs: I'm only trying to let things I care about sell themselves. There's a difference between force-feeding somebody conclusions versus giving them the facts that they can use to, hopefully, arrive at conclusions. I sometimes poke fun at a tech, but I then proceed to use that exact tech on stage. So, I'm poking fun at myself, ultimately.

You can point people in a certain direction, but I know what it's like to have gone to a talk and felt like I just had the wool pulled over my eyes. I feel that way with slideware talks. You walk out at the finish line at the same place, but you don't quite know how you got there, so you feel like something was missing...