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

Matt's stage outfits

Geertjan Wielenga: I've seen you wearing a suit and drinking whiskey while presenting a session, which was a unique combination. What was the value-add of that?

Matt Raible: That was an idea I came up with for JHipster. I was really intrigued by JHipster because it was basically what I was doing for clients.

I was either doing Angular frontends or Spring Boot backends. I could never quite get any clients to sign up for me doing both. I really wanted to promote myself because I was an independent consultant at the time and I wanted to write a book on JHipster.

I was added to the project as a committer. Then, when I was first doing a talk, I was thinking, "Well, they have the word 'hipster' in there, so I'll do that: get hip with JHipster."

"By the end, I was a hip JHipster developer drinking whatever beer was hip in the country I was in!"

—Matt Raible

I decided I should be an old-fashioned Java developer...