Jim by Norwich Artist Charli Vince

James Seconde

Developer Advocate | Speaker | Writer | Podcast Host

A Fifth Pillar of Developer Relations

On responsibilies in DevRel for Advocates.

James Seconde

9-Minute Read

Jim presenting

I don't think anyone could have predicted how bad 2020 would end up, but it certainly brought to light some thinking about how I'd like Developer Relations to change.

There is a specific reason for writing this article, but I realised that the topic it covered went a lot deeper, and exposes new trends in tech while raising some fairly important questions to consider both in Developer Relations and Web Development.

Hooray for Hugo

So, the original reason for writing this is that returning visitors might have noticed a shiny new Dev Theatre site. It's written in Hugo, using the fantastically functional and beautiful theme hugo-future-imperfect-slim. To give a slight bit of gushing for the tech: I LOVE this JAMStack. Golang compiles this site at lightning speed - at least five times faster than what was a rather over-engineered Gatsby codebase. I've found it to be a hugely positive experience, at a time when there have been few positives, so let's get this out of the way:

Gatsby

The reason the site is migrated is the whistle-blowing from a contractor on the running of Gatsby as a company. You can find this here.

OK, OK: companies can be badly run, it happens. But what was it about this incident that made it any different, for me at least?

In the Bay Area, startups are regularly going from a CEO founder and co-founding CTO one minute, to whispering the word “blockchain” out into the Venture Capital Wild West to be rewarded with millions of dollars in other people's cash. The company somehow scales to having 100 employees, maybe some scattered around the globe remote, hiring extremely expensive DevRel with what seems like a roll of the dice when it comes to how that scaling has been structured. From this perspective, Gatsby scored the right technologies at the right time, securing its name as the React JAMStack and massively scaling. The whistleblower in this case identifies a host of problems that come with the disogranisation that brings, but arguably the most damage was done with the response. The response is what made me realise that there are some topics to consider when you're involved in Developer Relations, and Gatsby serves as fairly good case study.

Here is the response from Gatsby CEO Kyle Matthews: https://twitter.com/kylemathews/status/1294006966310731776

I'm always fascinated with the response companies and/or individuals concoct when faced with a major PR crisis. There is a tendency for Politicians, for instance, to give spectacular insights into their lack of self awareness by either doubling down or responding with something utterly moronic that they think people will swallow at face value.

So in this case, with Gatsby, you'd have thought that the alarm bells went off at GatsbyHQ, and the board would push the button to get a Public Relations consultancy to handle the hot potato.

What actually happened was the CEO put out a statement saying, to words of this effect: “We are sorry that you feel offended, running this business is hard, we're launching a Cloud Product soon by the way, we are not actually going to do anything about the points raised because we don't care”.

PR Damage is administered

I wonder what effect Gatsby thought it would have? Realistically, what happened next was painfully predictable. End users on Twitter started discussing migrating from Gatsby to other technologies immediately (including me). Sounds harmless (what impact could I have, just being the end user of an Open Source framework?) but coupled with the aforementioned impending launch of Gatsby Cloud, one of it's first commercial products suddenly potentially lost a massive chunk of it's users, ergo it's revenue. Elsewhere, major influencers in the worlds of Developer Relations, DevOps, Javascript, InfoSec/DevSecOps - you name it - were quick to fire ridicule on the handling of it all.

2020: a year of confusion

The Gatsby fallout is really just another tech botch to add to what has been a year of upheaval. We've had companies slow to act on COVID-19 (including in the DevRel space, companies that I shall leave nameless hiring in the middle of the pandemic with the requirement to be based in the Bay Area only, so presumably you start remote in San Francisco but when this all blows over you have to be on site which makes absolutely no sense), we've had a deluge of companies completely at odds about what “to do” about Black Lives Matter (the most baffling probably being TeeSpring pulling ANTIFA T-shirts because they're political, while continuing to sell QAnon and other far Right Wing stuff like White Pride merchandise which presumably doesn't qualify).

We also had the attempted launch of “Genderify", a seemingly pointless API that would attempt to guess your binary gender based on a name. One user was quick to point out that they were identifed as female, until they added “Dr” as a prefix, at which point it regendered them male. When challenged on this, the developers completely washed their hands of it and said it was simply the data doing the talking, not their product. Genderify not surprisingly didn't last long, presumably sinking with a wad of Ventre Capital money flushed down the toilet.

On a similar front in product, we had one of Intercom‘s Product owners vomiting out an outrageous display of bravado on Twitter for a launch aimed directly at a competitor, Zendesk, about how terrible their product is and how amazing Intercom's was. This misplaced chunk of my-Dad-is-bigger-than-yours was at least correctly handled by Intercom, who pulled the thread and apologised for getting the tone wrong.

In the Developer Relations space, Google decided to hide when one of it's Advocates blew the whistle on a harrowing description of violent abuse at the hands of one of their other employees, presumably (at first) deemed too important to immediately fire.

Local to my tech ecosystem haunts, the Laravel framework found some new heroes in the form of the Larabelles usergroup, which was shot down by a load of predicable “replyguy” responses asking why there was a need for women to have their own usergroup, while seemingly unaware that the very nature of what they were doing was answering their own question. There has been a string of these recently, which in context this year isn't particularly more than any other year going back to the dawn of software development, but it still irks. One of the points given to me by Michelle Sanver, former President of PHPWomen raised was that these sorts of things are becoming more prominent as women and LGBT developers are now more confident to speak out against such bigotry.

Developer Relations and PR as a fifth pillar

So, all of this raises an important feature of DevRel that I've not actually seen discussed at great length: PR. There are “Four pillars” of DevRel commonly cited, identified by Matthew Revell's Hoopy consultancy in April 2019. These are:

  • Outreach
  • Community
  • Product
  • Education & Support

What these incidents are bringing to light is that Developer Relations practitioners are, in most cases, the face of the company they work for, and that is a big responsibility. There is harmony on both sides when it comes to DevRel - the company have their role representing them on stage at conferences and meetups, while experienced Developer Advocates have become massive influencers within the world of software development, and use that to promote the company.

Take, for instance, the approach of how Developer Advocates are presented in Mary Thengvall‘s DevRel Bible, “The Business Value of Developer Relations: How and Why Technical Communities Are Key To Your Success". It presents, on the cover, illustrated likenesses of leading figures in DevRel who are interviewed in the book. The superstars appear to be us - that's how much influence we're supposed to be wielding.

I can give you a personal example of this in action - take, for instance, Cassidy Williams moving to Netlify. Her trademark humour started to be teased out of the Netlify corporate Twitter account, and it was clear without announcing it that Cassidy was now using it. She's a well known name in tech, and so personally now I associate Netlify (which hosts this site) with Cassidy, her skills and her humour and openness to being approached for advice. Sometimes Advocates (depending on their roles) are even first line support for a lot of developers they've formed relationships with.

That is indeed a lot more power than sometimes we're aware of. If that's the case, we really need a Fifth Pillar:

  • Public Relations

Kindness & Influence for good

We need that pillar in our arsenal of skills because it's a bigger burden to carry than some of us might be aware of. Practitioners of DevRel do need to adhere to the “relations” part of the role, because if we misuse the platform we're building for ourselves then we're not advancing the industry as a whole - which is something that as influencers I believe we have the power to do. Misusing that platform or throwing controversy on top of it doesn't go unnoticed: just ask “Uncle” Bob Martin, Greg Sidelnikov or Richard Stallman.

At NorDev Conference this year I saw Jon Skeet talk on Kindness, and I believe in Developer Relations empathy is a core skill we really should all have. It goes hand in hand with the responsibility of carrying that Public Relations profile of your employer - there's something less for them to worry about if you carry out your education to other developers with kindness, patience and understanding of others. This goes beyond just patience with others’ code skills - we're leading by helping others regardless of race, religion or gender identity at a employer that also understands the same core values that we do. Hopefully.

A curriculum

I think what I'd like to see is PR awareness as part of DevRel; I'm not stating that we should all be PR experts (we already need to maintain enough skillsets across a broad range), because in DevRel personalities shine through. I'd say we don't want to use PR as a tool to weather storms like companies and politicians do: the objective is the awareness to stop them in the first place.

How does one go about scoping what that looks like? Well, that I would like to discuss: feel free to hit me up!

Here's hoping for a kinder 2021.

Recent Posts

categories

About

Hi! I'm James. I do Developer Relations and Dev Experience stuff for Jump24 in Birmingham, UK.