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

Honesty about bugs

Mark Heckler: I will say that at Pivotal, we have well-developed components that very sharp people have poured years of effort and development into. So, the rough edges aren't usually as much of a problem.

When it comes to new projects, we have Project Riff and Knative. Things like that are being spun up and created early on. In those cases, you pretty much expect there to be a few edges that poke out and surprise you. When you do run into those issues, it makes sense to just say, "If you're using this in this use case, you might want to reconsider until this particular thing gets fleshed out better."

"I don't think you do anybody any favors by not telling them when there are gaps."

—Mark Heckler

These projects are still in early development. Obviously, you want to put your best foot forwards, but ultimately, I don't think you do anybody any favors by not telling them when there are gaps, or particular issues...