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

Knowing when to retire a talk

Rabea Gransberger: It's just a feeling for me. Usually, I've been submitting a talk for around two years, then, at some point, I just stop because I don't want to hear it again myself or the topic is out of date.

Eventually, the "Java 9 Modules" talk will be out of date, when everybody knows how to create Java modules, and then I will have to stop it. But with the code reviews talk, for example, it's funny because I think that it was in a very good state when I gave it for the last time. It was a very good feeling. Before that, I always had the feeling that I didn't like the talk myself. I got very good feedback about the talk from the conference rating systems and so on, so I continued to give the talk, but I was never really satisfied with the talk myself.

Geertjan Wielenga: If you were to describe yourself at a party, what would you say that you do?

Rabea Gransberger: That's really difficult...