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

Technical difficulties during a talk

Matt Raible: I've had a total of one person attend before and I just said, "You should go to another session!"

I think the biggest problem that I've had was laptop difficulties in 2005. I was just comparing web frameworks, but I was using a Mac, and the Macs weren't on Intel yet and were so slow. Things just beach-balled so much that I was apologizing to the audience. That started 30 minutes in. What came next was two more hours of me fumbling around and even trying a different laptop because I did have a backup, knowing that this might be a problem.

That was the ultimate crash and burn. It wasn't all over Twitter because Twitter didn't exist, but there was plenty of talk about it. It sucked, but that was probably my worst experience.

I'm doing a bunch of JHipster stuff tomorrow at the Utah Java Users Group, and what I've learned to do is just bring swag, such as t-shirts and books. If I know that it&apos...