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

Successful talk titles

Geertjan Wielenga: Do you try to make your titles and your content as broad as possible, to attract as many people as possible, or do you try to attract a few people who are going to be really focused on that particular topic?

Matt Raible: I certainly go with keywords. I've noticed that conference talks are very similar to blog post titles for SEO. You get more readers if you have the words "Angular" and "Spring Boot" in the title.

For conference talks, if you put the word "JHipster" in there without "Angular" and "Spring Boot," you're not going to get that many people coming. Keywords definitely attract people differently.

I might reuse a blog post. That's what I've been doing lately. I'll take a blog post as the main driver of the content, turn it into a presentation, and do the tutorial as a live coding exercise.

Geertjan Wielenga: How do you decide that you've done a session...