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

Handling unexpected questions

Mark Heckler: Yes, but everybody who's been in this field for any length of time has had somebody ask a question that initially seemed to have a very easy answer. In that situation, you think that you know the answer from start to finish and you're so proud of yourself. You give the answer, then they reply, "Yeah, but we're using X."

You think, "Oh my gosh, I didn't know anyone was using X for that!" Again, assumptions are your enemy.

You should never, even when you think you have the full answer, give your answer right away. There may be unique constraints that invalidate everything you thought you were providing of value. It's a good idea to learn more and get the full scoop before you actually prescribe something that will solve the pain area.

Geertjan Wielenga: Let's say that someone reading this discussion thinks that this is an interesting career path to follow. What traits or skills do they...