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

The qualities of a good talk

Rabea Gransberger: It means that the speaker is very knowledgeable and that he or she has a well-prepared talk, and they don't skip some of the answers that I would actually expect to have given to me.

A great talk should also match the abstract. Plenty of speakers give talks that don't match their abstract at all because they don't read it again. They submit something for a conference, half a year before the conference, and when they prepare the talk, they have a different idea for the talk in their mind because it developed over that half year.

If a talk doesn't match the abstract anymore, then it's not good for the audience. The audience is at the talk because they expect something that they read in the abstract. Sometimes, some of the points that were raised in the abstract are not addressed in the talk.

What I had to work on, after giving my first talk, was that I was very nervous at the beginning. When I'm very nervous, I tend...