A couple of years ago, I finally became a developer advocate after many years of trying to get closer to developer relations. I also got a chance to tell the story of my path to this role in a video on the Google Cloud Tech YouTube channel.

Currently, I'm on leave from work. And since I can't do work related activities on leave, I have been pondering my value and values as a developer advocate. I'm also making my way through the book Developer Relations: How to Build and Grow a Successful Developer Program by Caroline Lewko and James Parton and I thought it might be worthwhile for myself and others if I put these ideas down in a blog.

Job Title & Terms

There are a couple of titles that seem to be used interchangeably in the world of developer advocacy. Because I like word play and I'm a bit of a pedant, here are my thoughts on how they relate to me.

Developer Relations (DevRel) - This has become the overall umbrella for several related things when companies are trying to connect with developers better. And, since I currently don't want to be head of any departments, I'll just say that I'm in DevRel but that's not necessarily my title.
Developer Relations Engineer (DRE) - Officially, this is my current title with Google Cloud. I don't mind it. It reminds me and others that I am still an engineer and like doing tech work. But, it is still more of the umbrella term and I could be focusing on things that might not play to my strengths or values.
Developer Evangelist - This is the term I first heard when I learned it was an actual role. I jokingly liked it because of my wrestler name but for me, it seems a little bit too much like a snake oil salesman. It's a role I can play for laughs but I really don't want to sell snake oil. I want to help developers grow and succeed.
Developer Advocate (DA) - This is my preferred title, and the one I use as my official title where one is asked for. I like that it points to my position as an advocate for developers and their needs. Last year, I could (not completely unrealistically) joke that I also specialized as a Canadian Developer Advocate but that might just be my Canadienthusiasm even though I'm from the States.
Tech Muse - This isn't a term used very much, but enough that I couldn't get it as a username on social platforms. This is a term I use to describe myself and a goal of what I strive to be when I'm in front of other developers.
B2D Sales - Business to developer sales. From terms like B2B and B2C, marketing to developers is somewhat of a hybrid of the two.

My Values

Developers are the creators of innovation. To create, Developers need tools. Developer tools demand Developer Relations.

Perhaps I'm biased. I've been a developer since 2005. I think that developers are core to making new great tech. A developer is an artist who paints with code and technical know how. A developer works with other artists, like graphical designers and artists, QA, writers, and more to create these multimedia pieces of art. I should create a post about my hypothesis regarding the art/business spectrum, but business is usually what makes things less exciting while helping to actually release stuff.

I value inspiring that creativity. I'm excited about the things that people create and do with tech, or otherwise. In fact, my former podcast, The Seattle After Party, was all about what interesting things people were creating and doing (in the Seattle area). My goals should align with me being something of a tech muse in all the work I do for the role.

My Strengths

The first, and main reason I wanted to get into developer advocacy is because I am a performer by nature and love being in front of an audience. Through my training as a pro-wrestler, improviser, and other performance arts I've learned to create and tell a story based on what the audience needs. I also love meeting developers face to face to talk about what they are working on. Hopefully, I can be a bit of a tech muse during these interactions.

Those actions are almost always full of humor, joy, and play. This is me at my core, and all my favorite demos and workshops have this at their heart as well. I find that this helps people learn new tech (and new things in general). Make it silly. Make it fun. But, just make it. That is my advice to people trying to learn how to code when I'm asked online.

My Weaknesses?

I am neurodivergent. I have ADHD. I was late diagnosed in my 40s, so I have many coping mechanisms I've built up over the years. I succeeded before I was diagnosed. So, there are some nuggets of wisdom there. But, I also have become burnt out at work, or depressed, or anxious. So, these mechanisms may not be completely healthy. That's why I am exploring my values so that I can better succeed in the future and stay in a more consistent state.

Me standing in front of a PA mixer at Guitar Center in the 90s

One consistent thing I've found is that I don't want to be a salesperson. At least, not the stereotypical salesperson that sells the sizzle and not the steak or straight up lies to people to get sales. I've done sales before. It was retail B2C sales in a music store, and I eventually honed myself to be a top salesperson through taking care of customers actual needs. I once sold a $16K+(90s money) home studio setup to a gentleman and he went through me because I looked at what he actually needed and didn't try to sell him more than he needed just because he had the money. My experience with developers is, they don't like to be sold sizzle. They want to know if the steak is right for them. If they are vegetarian, it isn't. But, they might have colleagues who it is perfect for.

Other Important Items

To the community, I represent the company To the company, I represent the community I must have both of their interests in mind at all times

Me with the team in Ottawa getting ready to run a workshop event.

I know that to the community, I represent Google at the moment. To the company, I know they rely on me to help bring the voice of the community. The company also knows that I represent them when I'm in the community. So, they want me to show them in the best light. This requires me to get better at my craft.

My craft requires skills that I am good at (presenting and performing), skills I've shown I can do (writing blogs, writing code, writing scripts, writing workshops, sales & marketing), and things I'm not so good at (data gathering). It is important that I continue to get better at the skills that aren't my best while providing the most value with the skills that I am good at. By following my values, rather than mandating to myself what I should do, I am likely to have more success with my personal growth.

Conclusion

I have quite a bit of room to grow in this role. I'm surrounded by lots of great folks in the tech and devrel world who I can learn from. I will continue to post to my various social media areas my thoughts on being a tech muse. What about you? What are your values? Please share with me and I will continue to share with you.

My Developer Advocacy