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

Tim's tips for progressing to advocacy

Geertjan Wielenga: Based on your experience, what would be the best way to progress from being a developer to being an advocate?

Tim Berglund: If this profession sounds like a good idea to you, then it probably is. That's one of the nice things about developer advocacy. There's a large community of developers who think, "I guess I might be able to give a talk, but doing that work full-time sounds terrible." If anybody does want to do this full-time, then they should pursue it. They are probably qualified.

The way you start is to make up a talk on something. If the work that you do is with very bread-and-butter tech, you may think, "It's a good tech, but it's not super cutting edge. The world already has a Josh Long talking about Spring. I'm not going to be him overnight. How am I going to make something interesting about my day job?"

My advice is that if the code that you write in your day job isn...