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

Ethical considerations

Jennifer Reif: I think it's my role to show what is best practice and show code examples. Other people can get up on stage and present Neo4j as a product, but I'm really showing users what the tool was designed to do. Much of the time, as speakers, we've built these integrations ourselves. Therefore, that often makes us the experts on how the code works. This aspect gives us a leg up when we're speaking.

As far as ethics go, we want people to learn this stuff. We want people to be able to build projects and capabilities with the tools. Our goal is to show people what can be done.

Geertjan Wielenga: If there's a bug in the product and you're up on the stage, do you skirt around that bug in your demo? Obviously, you're not going to go and highlight all the bugs in the product. What is the middle ground there? How do you handle that situation?

Jennifer Reif: I think that's where you go back to thinking about what the product was designed...