├── .gitignore ├── gbu-developer-advocacy.key ├── gbu-developer-advocacy.pdf ├── profiles ├── arun_gupta.adoc ├── bruno_borges.adoc ├── hadi_hariri.adoc ├── josh_long.adoc ├── mano_marks.adoc ├── mark_heckler.adoc ├── markus_eisele.adoc ├── matthias_steiner.adoc ├── profile.adoc ├── readme.adoc ├── simon_maple.adoc ├── sven_peters.adoc ├── trisha_gee.adoc └── vlad_mihalcea.adoc └── readme.adoc /.gitignore: -------------------------------------------------------------------------------- 1 | .idea/ 2 | *.iml 3 | -------------------------------------------------------------------------------- /gbu-developer-advocacy.key: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/arun-gupta/devrel/66e509c3c37c86837f112ceb5ad65ba39feb44a8/gbu-developer-advocacy.key -------------------------------------------------------------------------------- /gbu-developer-advocacy.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/arun-gupta/devrel/66e509c3c37c86837f112ceb5ad65ba39feb44a8/gbu-developer-advocacy.pdf -------------------------------------------------------------------------------- /profiles/arun_gupta.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile 2 | 3 | . *Name*: Arun Gupta 4 | . *Twitter*: http://twitter.com/arungupta[@arungupta] 5 | . *Blog*: http://blog.arungupta.me[Miles to go ...] 6 | . *Github*: http://github.com/arun-gupta 7 | . *How long you've had a formal title?*: 9+ years 8 | . *Preferred airline*: United 9 | . *Favorite IDE*: NetBeans, IntelliJ, Sublime Text, Eclipse 10 | . *Favorite (natural) Language(s)* 11 | .. English 12 | .. Hindi 13 | . *Favorite (programming) Language(s)* 14 | .. Java 15 | . *Favorite cuisine* 16 | .. Protein and fiber-rich, stay away from red meat 17 | . *Three most important tools/techniques for Developer Advocacy*: 18 | .. Try the bleeding edge tools and feel the developer's pain before they do. File tons of bugs. 19 | .. Keep OOTB experience for your products/technologies *really* simple 20 | .. Stay hungry, stay foolish - Learn, learn, learn all the time! 21 | . *How do you create scalable content?* 22 | .. Create content once, reuse/syndicate wherever possible 23 | .. Typically follow the flow: Blog -> Slides -> Hands-on workshop -> Talk at an event 24 | .. Instead of making it a product pitch, keep the topic generic and relevant to current topics 25 | . *How do you measure Developer Advocacy?* 26 | .. Scalable content (blogs, articles, webinars, hands-on labs) 27 | .. Twitter mentions, impressions, growth of followers 28 | .. Page/webinar views, developer outreach at talks 29 | 30 | -------------------------------------------------------------------------------- /profiles/bruno_borges.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile: Bruno Borges 2 | 3 | . *Name*: Bruno Borges 4 | . *Company*: Oracle 5 | . *Twitter*: https://www.twitter.com/brunoborges[@brunoborges] 6 | . *Email*: bruno.borges@gmail.com 7 | . *Blog*: https://blogs.oracle.com/brunoborges[blogs.oracle.com/brunoborges] 8 | . *Github*: https://github.com/brunoborges[https://github.com/brunoborges] 9 | . *How long you've a formal title?*: Never had. 10 | . *Preferred airline*: American Airlines 11 | . *Favorite IDE*: It depends, but usually NetBeans/Eclipse, and text editors (vim/Sublime). 12 | . *Favorite (natural) Language(s)* 13 | .. Portuguese (native) 14 | .. Spanish 15 | .. English 16 | . *Favorite (programming) Language(s)* 17 | .. Java 18 | .. Javascript 19 | .. Shell scripting 20 | . *Favorite cuisine* 21 | .. Red meat and beer 22 | . *Three most important tools/techniques for Developer Advocacy*: 23 | .. Communication outreach, and beyond comfortable zone. (such as communicating with people from different languages) 24 | .. Technical knowledge beyond usual "hello world". (some real world experiences are a great differentiator to have) 25 | .. Great networking with other organizations inside your corporation (dev advocacy is also about internalizing feedback) 26 | . *How do you create scalable content?* 27 | .. Social media, blogging, writing technical articles, externalizing real world use cases, presentations. 28 | . *How do you measure Developer Advocacy?* 29 | .. By how much you can influence Products Roadmaps 30 | .. By how many developers you can help to achieve their goals with the products you advocate for 31 | .. Quality and quantity of successful customers' projects 32 | -------------------------------------------------------------------------------- /profiles/hadi_hariri.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Hadi Hariri 2 | 3 | . *Name*: Hadi Hariri 4 | . *Company*: JetBrains 5 | . *Twitter*: https://www.twitter.com/hhariri[@hhariri] 6 | . *Email*: mail@hadihariri.com 7 | . *Blog*: https://hadihariri.com[http://hadihariri.com] 8 | . *Github*: https://github.com/[https://github.com/hhariri] 9 | . *How long you've a formal title?*: Developer Advocate for 6 years. 10 | . *Preferred airline*: Air France 11 | . *Favorite IDE*: IntelliJ IDEA 12 | . *Favorite (natural) Language(s)* 13 | .. English 14 | . *Favorite (programming) Language(s)* 15 | .. Kotlin, C#, JavaScript 16 | . *Favorite cuisine* 17 | .. Persian 18 | . *Three most important tools/techniques for Developer Advocacy*: 19 | .. Knowing how to communicate 20 | .. Enjoying learning 21 | .. Not being a pundit 22 | . *How do you create scalable content?* 23 | .. Scalable in time: Create content that doesn't have an expiry date (every JavaScript framework does) 24 | .. Scalable in reach: Create content that people want to share (nothing boring!) 25 | .. Scalable in usage: Create content that can be repurposed (a blog post can form part of a book) 26 | . *How do you measure Developer Advocacy?* 27 | .. Depends on what you want to measure, and if those things measuring actually have any value. KPI's are often used for CYA's more than anything else. 28 | -------------------------------------------------------------------------------- /profiles/josh_long.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Josh Long 2 | 3 | . *Name*: Josh Long 4 | . *Company*: Pivotal 5 | . *Twitter*: https://www.twitter.com/starbuxman[@starbuxman] 6 | . *Email*: josh@joshlong.com 7 | . *Blog*: https://joshlong.com[Code, Coffee] 8 | . *Github*: https://github.com/joshlong[https://github.com/joshlong] 9 | . *How long you've a formal title?*: Spring Developer Advocate since 2010, engineer since I could wield a computer 10 | . *Preferred airline*: UNITED 11 | . *Favorite IDE*: IntelliJ IDEA, Spring Tool Suite, Netbeans 12 | . *Favorite (natural) Language(s)* 13 | .. English (native) 14 | .. French 15 | .. Spanish 16 | . *Favorite (programming) Language(s)* 17 | .. Java 18 | . *Favorite cuisine* 19 | .. Everything that is delicious and organic 20 | . *Three most important tools/techniques for Developer Advocacy*: 21 | .. impassioned curiosity 22 | .. make friends 23 | .. technology 24 | . *How do you create scalable content?* 25 | .. Creating talks that are relevant to a broad audience 26 | .. Supporting talks with blog-posts and articles 27 | .. Syndicate content through hubs (internally and externally); e.g. DZone, InfoQ, the http://spring.io/blog[Spring Blog] 28 | .. write http://shop.oreilly.com/product/0636920038252.do[books] and deliver https://www.safaribooksonline.com/library/view/building-microservices-with/9780134192468/part00.html[video trainings] 29 | . *How do you measure Developer Advocacy?* 30 | .. Basic Metrics (Social Media Reach, PageViews, Downloads, etc.) 31 | .. Extended Marketing Metrics (company internal) 32 | .. Event Metrics (Session Ratings, Tweets) 33 | -------------------------------------------------------------------------------- /profiles/mano_marks.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile 2 | 3 | . *Name*: Mano Marks 4 | . *Twitter*: http://twitter.com/ManoMarks[@manomarks] 5 | . *Blog*: http://manomarks.github.io/[Random Nodes] 6 | . *Github*: http://github.com/ManoMarks 7 | . *How long you've had a formal title?*: 9+ years 8 | . *Preferred airline*: Hate them all 9 | . *Favorite IDE*: Atom, Sublime Text 10 | . *Favorite (natural) Language(s)* 11 | .. English 12 | .. Hungarian 13 | . *Favorite (programming) Language(s)* 14 | .. JavaScript 15 | . *Favorite cuisine* 16 | .. Hard to choose, I'm a foodie, but I'd say Italian or Mexican 17 | . *Three most important tools/techniques for Developer Advocacy*: 18 | .. Always be coding 19 | .. Listen 20 | .. Learn 21 | .. Talk 22 | . *How do you create scalable content?* 23 | .. Go where your developers are 24 | .. You can't ignore events, but online content is the only thing that scales 25 | .. Partner, partner, partner 26 | . *How do you measure Developer Advocacy?* 27 | .. Views and engagement on videos and content 28 | .. People spoken to 29 | .. Useage of product 30 | .. Definitely not "share-of-voice" 31 | -------------------------------------------------------------------------------- /profiles/mark_heckler.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile 2 | 3 | . *Name*: Mark Heckler 4 | . *Company*: Pivotal 5 | . *Twitter*: https://twitter.com/MkHeck[@MkHeck] 6 | . *Email*: mark@thehecklers.org, mark.heckler@gmail.com 7 | . *Blog*: http://www.thehecklers.org[http://www.thehecklers.org] 8 | . *Github*: https://github.com/hecklerm[https://github.com/hecklerm] 9 | . *How long you've had a formal title?*: Title for 2 years, responsibility for 5, developer since I got my first computer! 10 | . *Preferred airline*: United 11 | . *Favorite IDE*: IntelliJ IDEA, Spring Tool Suite, NetBeans 12 | . *Favorite (natural) Language(s)* 13 | .. English 14 | .. Español 15 | . *Favorite (programming) Language(s)* 16 | .. Java 17 | .. JavaScript 18 | . *Favorite cuisine* 19 | .. Indian food of nearly any kind 20 | .. Mexican food of nearly any kind 21 | .. Chinese food of nearly any kind 22 | .. Food of nearly any kind 23 | . *Three most important tools/techniques for Developer Advocacy* 24 | .. Insatiable thirst for knowledge 25 | .. Burning desire to share that knowledge 26 | .. Ability to understand and empathize with another's situation and share relevant information clearly and _usefully_ 27 | . *How do you create scalable content?* 28 | .. Create content with broad relevance for greater reach, and more importantly, greater applicability 29 | .. Create content that can be adapted to multiple formats: concept documents, quick tips, deep-dive "how to" articles, short presentations, and workshops 30 | .. Leverage social media to get the word out about existing content and solicit feedback and ideas for future content 31 | . *How do you measure Developer Advocacy?* 32 | .. Basic Metrics (Social Media Reach, PageViews, Downloads, etc.) 33 | .. Extended Marketing Metrics (company internal) 34 | .. Event Metrics (Session Ratings, Tweets) 35 | -------------------------------------------------------------------------------- /profiles/markus_eisele.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Markus Eisele 2 | 3 | . *Name*: Markus Eisele 4 | . *Company*: Red Hat 5 | . *Twitter*: https://www.twitter.com/myfear[@myfear] 6 | . *Email*: markus@jboss.org 7 | . *Blog*: https://blog.eisele.net[blog.eisele.net] 8 | . *Github*: https://github.com/myfear[https://github.com/myfear] 9 | . *How long you've a formal title?*: Developer Advocate since 2 years. Working in that space since more than 10. 10 | . *Preferred airline*: LUFTHANSA 11 | . *Favorite IDE*: NetBeans, Notepad++, Eclipse with JBoss Tools 12 | . *Favorite (natural) Language(s)* 13 | .. German (native) 14 | .. English 15 | . *Favorite (programming) Language(s)* 16 | .. Java 17 | . *Favorite cuisine* 18 | .. Everything that is delicious and organic 19 | . *Three most important tools/techniques for Developer Advocacy*: 20 | .. People Skills 21 | ... Communication (Listening, https://en.wikipedia.org/wiki/Four-sides_model[the four-sides model]) 22 | ... Presenting 23 | ... Conflict Management (How to respond in challenging situations) 24 | .. Technology (You have to know the stuff, that you're talking about) 25 | .. Living to learn something new over and over again. Be curious. 26 | . *How do you create scalable content?* 27 | .. Creating talks that are relevant to a broad audience 28 | .. Supporting talks with blog-posts and articles 29 | .. Syndicate content through hubs (internally and externally); e.g. DZone, planet.jboss.org 30 | . *How do you measure Developer Advocacy?* 31 | .. Basic Metrics (Social Media Reach, PageViews, Downloads, etc.) 32 | .. Extended Marketing Metrics (Company internal) 33 | .. Event Metrics (Session Ratings, etc.) 34 | -------------------------------------------------------------------------------- /profiles/matthias_steiner.adoc: -------------------------------------------------------------------------------- 1 | = Cloud Platform Advocate Matthias Steiner 2 | 3 | . *Name*: Matthias Steiner 4 | . *Company*: SAP SE 5 | . *Twitter*: https://www.twitter.com/steinermatt[@steinermatt] 6 | . *Email*: matthias.steiner@sap.com 7 | . *Blog*: http://inscope.net[inscope.net] 8 | . *Github*: https://github.com/steinermatt[https://github.com/steinermatt] 9 | . *How long you've a formal title?*: Rolling as 'Cloud Platform Evangelist' since 2012 year, been working in that space for more than a decade now. 10 | . *Preferred airline*: LUFTHANSA 11 | . *Favorite IDE*: Eclipse (yeah, call me old-fashioned) 12 | . *Favorite (natural) Language(s)* 13 | .. German (native) 14 | .. English (fluent) 15 | . *Favorite (programming) Language(s)* 16 | .. Java 17 | . *Favorite cuisine* 18 | .. Pretty much everything... plus: meat lover 19 | . *Three most important tools/techniques for Developer Advocacy*: 20 | .. Communication, communication, communication (incl. cultural awareness) 21 | .. Being an autodidact and embracing life-long learning 22 | .. Staying young at heart & keeping the excitment about new tech 23 | . *How do you create scalable content?* 24 | .. Avoid product pitches, instead talk about topics of broader interest 25 | .. Cross-reference related materials, give proper credit & attribution 26 | .. Tagging, tagging, tagging 27 | . *How do you measure Developer Advocacy?* 28 | .. How to measure influence? Tough one to crack... (don't you dare say: Klout score!) 29 | -------------------------------------------------------------------------------- /profiles/profile.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile 2 | 3 | . *Name*: 4 | . *Twitter*: 5 | . *Blog*: 6 | . *Github*: 7 | . *How long you've had a formal title?*: 8 | . *Preferred airline*: 9 | . *Favorite IDE*: 10 | . *Favorite (natural) Language(s)* 11 | .. ONE 12 | .. TWO 13 | . *Favorite (natural) Language(s)* 14 | .. ONE 15 | .. TWO 16 | . *Favorite cuisine* 17 | .. ONE 18 | .. TWO 19 | . *Three most important tools/techniques for Developer Advocacy* 20 | .. ONE 21 | .. TWO 22 | .. THREE 23 | . *How do you create scalable content?* 24 | .. ONE 25 | .. TWO 26 | .. THREE 27 | . *How do you measure Developer Advocacy?* 28 | .. ONE 29 | .. TWO 30 | .. THREE 31 | 32 | -------------------------------------------------------------------------------- /profiles/readme.adoc: -------------------------------------------------------------------------------- 1 | = Profiles of Developer Advocate 2 | 3 | . link:markus_eisele.adoc[Markus Eisele] 4 | . link:simon_maple.adoc[Simon Maple] 5 | . link:arun_gupta.adoc[Arun Gupta] 6 | . link:vlad_mihalcea.adoc[Vlad Mihalcea] 7 | . link:josh_long.adoc[Josh Long] 8 | . link:sven_peters.adoc[Sven Peters] 9 | . link:hadi_hariri.adoc[Hadi Hariri] 10 | . link:bruno_borges.adoc[Bruno Borges] 11 | . link:mano_marks.adoc[Mano Marks] 12 | . link:mark_heckler.adoc[Mark Heckler] 13 | . link:trisha_gee.adoc[Trisha Gee] 14 | . link:matthias_steiner.adoc[Matthias Steiner] 15 | . Doris Chen 16 | . Baruch Sadogursky 17 | . Stephen Chin 18 | . Amanda Waite 19 | . Burr Sutter 20 | . Steven Citron-Pousty 21 | . Grant Shipley 22 | . Geertjan Wielenga 23 | . Tugdual Grall 24 | . Simon Ritter 25 | 26 | -------------------------------------------------------------------------------- /profiles/simon_maple.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Simon Maple 2 | 3 | . *Name*: Simon Maple 4 | . *Company*: ZeroTurnaround 5 | . *Twitter*: https://www.twitter.com/sjmaple[@sjmaple] 6 | . *Email*: sjmaple@gmail.com 7 | . *Blog*: https://zeroturnaround.com/rebellabs[zeroturnaround.com/rebellabs] 8 | . *Github*: https://github.com/sjmaple[https://github.com/sjmaple] 9 | . *How long you've a formal title?*: Developer Advocate for 5 years. 10 | . *Preferred airline*: British Airways 11 | . *Favorite IDE*: Eclipse 12 | . *Favorite (natural) Language(s)* 13 | .. English 14 | . *Favorite (programming) Language(s)* 15 | .. Java 16 | .. Groovy 17 | . *Favorite cuisine* 18 | .. Anything cooked with local high quality ingredients 19 | . *Three most important tools/techniques for Developer Advocacy*: 20 | .. Communication - Both having the ability to succinctly describe technical concepts as well as listen an understand requirements and pain points. 21 | .. Trust - It's incredibly important developer advocates are respected in their field, credible and honest. 22 | .. Network - A developer advocate is only as good as their reach, through connections and contacts. 23 | . *How do you create scalable content?* 24 | .. Good content can be used in multiple ways. A blog post can turn into a whitepaper, that might be a great presentation. 25 | .. Content can be cross posted on different sites and syndicated through aggregate sites. 26 | .. The best way to make content live longer is through good SEO and social outreach. 27 | . *How do you measure Developer Advocacy?* 28 | .. Outreach - how many people does your content touch? Attendees, readers, twitter impressions, etc 29 | .. Conversion - how many people enter your community or site from a known source that go on to interact or purchase 30 | .. Awareness - Twitter followers, community members, content subscribers etc. 31 | 32 | -------------------------------------------------------------------------------- /profiles/sven_peters.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Profile 2 | 3 | . *Name*: Sven Peters 4 | . *Twitter*: http://twitter.com/svenpet[@svenpet] 5 | . *Blog*: http://svenpet.com[svenpet.com] 6 | . *Bitbucket*: https://bitbucket.org/sven_peters/ 7 | . *How long you've had a formal title?*: 4+ years 8 | . *Preferred airline*: Lufthansa 9 | . *Favorite IDE*: IntelliJ, Eclipse 10 | . *Favorite (natural) Language(s)* 11 | .. German (native) 12 | .. English 13 | .. Danish 14 | . *Favorite (programming) Language(s)* 15 | .. Java 16 | . *Favorite cuisine* 17 | .. everything without fish 18 | . *Three most important tools/techniques for Developer Advocacy*: 19 | .. engaging directly with the community (User groups, conferences, online communities, etc.) 20 | .. creating talks that are relevant for the audience (no product pitches) 21 | .. create tools to measure success, be sure what you want to achieve 22 | . *How do you create scalable content?* 23 | .. invest a lot of time in talk creation (slides, story, flow) to deliver it as often as possible 24 | .. make your talks so other people at your organization can give those (I can't clone myself, but the content can) 25 | .. teach other people how to tell stories, create tutorials, give presentations, etc. 26 | .. having in mind that talks can easily be adopted to different audiences / markets 27 | .. create online content from talks 28 | .. avoid prodcut pitches so the content is relevant and people like to share it 29 | . *How do you measure Developer Advocacy?* 30 | .. attendees at presentations, number of presentations, geographic outreach, market outreach 31 | .. online content visistors (blogs, articles, tutorials, slideshare, etc.) 32 | .. social media engement: twitter, hacker news, redit, etc.. 33 | -------------------------------------------------------------------------------- /profiles/trisha_gee.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Trisha Gee 2 | 3 | . *Name*: Trisha Gee 4 | . *Company*: JetBrains 5 | . *Twitter*: https://www.twitter.com/trisha_gee[@trisha_gee] 6 | . *Email*: trisha.gee@jetbrains.com 7 | . *Blog*: http://trishagee.com[trishagee.com] 8 | . *Github*: https://github.com/trishagee[https://github.com/trishagee] 9 | . *How long you've a formal title?*: Officially a Developer Advocate for 1 year, but been doing advocacy for 5 years 10 | . *Preferred airline*: British Airways 11 | . *Favorite IDE*: IntelliJ IDEA 12 | . *Favorite (natural) Language(s)* 13 | .. English. 14 | .. Currently learning Spanish. 15 | . *Favorite (programming) Language(s)* 16 | .. Java 17 | .. Groovy 18 | .. Kotlin 19 | . *Favorite cuisine* 20 | .. Curry (English-style) 21 | . *Three most important tools/techniques for Developer Advocacy*: 22 | .. The ability to break complex topics into something that's easy to digest and (preferably) applicable to the day-job 23 | .. Credibility - developers tend to listen best to those who are either developers themselves or have a proven 24 | understanding of the concerns of developers. 25 | .. Being approachable - so people can ask "stupid" questions and know they won't be laughed or sneered at. 26 | . *How do you create scalable content?* 27 | .. Personally I like to select a theme to follow which leads to presentations, blog posts and tutorials. For 28 | example, last year I picked "Java 8 in Anger" - it required an upfront investment of really understanding Java 8's 29 | features and what they might be useful for, but that investment paid off with a live-coding presentation which could 30 | be presented at almost any technical conference, a tutorial which could be run as a half or full day, and a series of 31 | blog posts, articles, and screencasts which explored various aspects of Java 8. 32 | .. Although they're a lot of work, live demos are scalable as they can be more easily presented remotely or worked 33 | into one or more screencasts. Screencasts and videos are a great way to reach many more people than a single 34 | conference. 35 | .. Content that applies outside of a single niche is more scalable - "Java 8 in Anger" lead to a lot of material, but 36 | it has little relevance for non-Java developers. I've created apps utilising a range of technologies working 37 | together (e.g. AngularJS, MongoDB and Groovy) which can mean that developers from a range of backgrounds pick 38 | something up. Also more general topics like Data Structures, how to design systems and how to select technologies are 39 | relevant for many techies and also less likely to go out of fashion. 40 | . *How do you measure Developer Advocacy?* 41 | .. You can use metrics like: page views; video watches; conference attendee numbers; Twitter followers; 42 | newsletter subscribers; links followed; downloads etc. But it's difficult 43 | to determine exactly how much benefit advocacy gives to the business bottom line - it's a form of pre-pre-sales, and 44 | could be a long time between someone seeing a presentation or reading a blog, and ultimately spending money on a 45 | product. How to measure the specific impact of advocacy on the revenue of the business that supports it is a difficult 46 | question to answer. 47 | 48 | -------------------------------------------------------------------------------- /profiles/vlad_mihalcea.adoc: -------------------------------------------------------------------------------- 1 | = Developer Advocate Vlad Mihalcea 2 | 3 | . *Name*: Vlad Mihalcea 4 | . *Company*: Red Hat 5 | . *Twitter*: https://www.twitter.com/vlad_mihalcea[@vlad_mihalcea] 6 | . *Email*: vlad@hibernate.org 7 | . *Blog*: http://vladmihalcea.com[vladmihalcea.com] 8 | . *Github*: https://github.com/vladmihalcea[https://github.com/vladmihalcea] 9 | . *How long you've had a formal title?*: Developer Advocate since 2 months. Ten years working experience. 10 | . *Preferred airline*: TAROM 11 | . *Favorite IDE*: IntelliJ IDEA 12 | . *Favorite (natural) Language(s)* 13 | .. Romanian (native) 14 | .. English 15 | .. French 16 | . *Favorite (programming) Language(s)* 17 | .. Java 18 | . *Favorite cuisine* 19 | .. Romanian 20 | . *Three most important tools/techniques for Developer Advocacy*: 21 | .. Expertize: You need to be very skilled in the field you are advocating 22 | .. Communication: Being a good listener and knowing how to deliver information, be it in a speech or a written document 23 | .. Charisma: Be friendly and helpful. 24 | . *How do you create scalable content?* 25 | .. Improving documentation and writing focused blog posts and tutorials 26 | .. Aggregating relevant content in a community newsletter 27 | .. Broadcasting articles on network channels: Twitter, Reddit. 28 | . *How do you measure Developer Advocacy?* 29 | .. Metrics (Number of downloads, twitter followers and impressions) 30 | .. Community engagement (blog posts, tutorials, courses). 31 | -------------------------------------------------------------------------------- /readme.adoc: -------------------------------------------------------------------------------- 1 | = Developer Relations Around The World 2 | 3 | Developer Relations, Developer Advocate, Developer/Technology Evangelist, Community Manager are some of the names given to the craft of people who make effective users of your technlogy. It could be a product, platform, API, a mobile application, website, or anything that you want to promote. 4 | 5 | == #DevRel Strategy 6 | 7 | === Strategy 8 | 9 | Content is king! Make sure it's SEO-optimized otherwise it's sitting in a silo. 10 | 11 | Three types of contents: 12 | 13 | - What 14 | - How 15 | - Wow 16 | 17 | === Tactics 18 | 19 | * Blogging - blogging cadence is important 20 | ** Talk about bleeding edge topics and show your technology is relevant there. 21 | * Speaking at conferences and meetups 22 | ** Track conference CFPs that matter to your audience. Some of the conferences have 6-8 months lead time. Most of the conferences would straight reject a product pitch. So your talk title/abstract should focus on solving a problem. 23 | ** Search for meetups relevant to your audience at meetup.com. Reach out to the meetup leader by sending an email to Organizers (link on the left panel of meetup page). You may consider speaking at the local meetup when speaking in a new city at a conference. 24 | * Podcasts - Software Engineering Daily 25 | * Webinars 26 | * Videos 27 | * Social media 28 | * Sample Applications 29 | * Demos 30 | * Answering questions on Forums and/or Stackoverflow 31 | * Ready-to-use slides, with speaker notes (1 slide, 5 slides, 30 slides) 32 | 33 | ==== SEO optimization 34 | 35 | Your content has to be SEO-optimized. Nobody will come to your website, unless you are Google or Facebook, if your content is not indexed by two search engines - Google and Bing. 36 | 37 | link:profiles/readme.adoc[Profiles of Developer Advocates] 38 | 39 | --------------------------------------------------------------------------------