Other terms

[chrisalexander]

Oooh, controversial!

I thought it would be worth mentioning there are some very similar roles - at least, to which this document as it stands could largely apply - which have different names.

While I realise they are not all necessarily the same, it might be worth pointing out for the uninitiated that such things exist and they can make their own minds up about it.

[codepo8]

Yep that was proven bu the Twitter thread. Personally I find this more confusing than helpful. Sooner or later you need to make a stand and call something something. The role of evangelist has been official in Microsoft and Yahoo for quite a while (well, I introduced it to Yahoo), Advocat came from Google.

They both are loaded with misconceptions. Evangelist sounds like you need to tell with hope for people to believe you, advocate assumes you need to tell your company what developers need. Both are things you need to do.

Are you a web designer or web developer, or front end engineer, or what? Sooner or later you'll get an official title that matches your HR framework anyways.

[chrisalexander]

The thing for me is that while there are these roles, which are very similar, there isn't really a term that encompasses them - not one that I am aware of that is sufficient for me at least.

I desperately don't want to group them all under something like "Developer marketing" but I just can't find something that sums it up.

Regarding this diff, I don't mind if it doesn't go in - I'm exploring what the community think of the topic a bit, and where this document fits in :)

[andypiper]

from https://dev.twitter.com/developer-advocate

Other companies have different name for this role: platform evangelism, developer relations, API evangelism. Wikipedia provides a (somewhat) neutral overview of the platform evangelism role at http://en.wikipedia.org/wiki/Platform_evangelism.