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

When technical glitches hit

Scott Davis: Resiliency is something we always talk about in software. I think resiliency is something you have to strive for as an instructor or as a conference speaker.

It's not avoiding technical glitches that makes you a pro: it's the grace and humor you use in reacting to the glitches when they inevitably happen. I've had a number of people come up to me after a talk that went badly and say, "I'm sorry that you had trouble up there on stage, but I probably learned more from watching you debug it in real time than if everything had gone right in the first place."

Nowadays, I take a screenshot of every website that I'm going to mention in my presentation and put it in my slides with a hyperlink. If I'm at a conference with good Wi-Fi, then I can click on the screenshot and seamlessly scroll around the live website as I talk about it.

If, on the other hand, I end up in a hotel conference room in the basement with crummy Wi...