Benefits of Joining and Staying in a Developer Program

More than 80 percent of developers tell Evans Data, in the Developer Relations Program Survey 2017, that they belong to one or more developer programs (free and/or paid). A majority of developers have consistently told Evans Data that they won’t use a product, service, platform, API, device, framework, library and other technologies if there isn’t an associated active developer community. The top reasons for joining and staying with a technology and a developer community are included in “The Four T’s”: technical support, technical information, training and tools. Being a part of a thriving developer community, developers tell Evans Data that there are three primary benefits that they report to their executives and managers: time saved, increased productivity and improved quality.


Time Saved

When your developer program provides great documentation, getting started guides, step by step tutorials, sample template projects, pre-built client and server libraries, videos, and code snippets programmers can save time learning your APIs, building applications and reusing code. In the Evans Data Developer Relations Survey 2017,  more than three quarters of developers report that they save time because of their membership. The savings amount to being able to get more work done each week. Being able to access latest updates, bug fixes, and workarounds allows developers to avoid wasting time trying to track down a known problem. Talking with other developers in program forums and newsgroups can also save hours of wasted time that others have already incurred.



Increased Productivity

Using great tools, SDKs and content helps developers streamline their design, development, testing and deployment work. Leveraging the work done by your R&D team and developer advocates to help community members results in increased productivity for themselves and their teams. In my years of experience and with feedback from community members, it always helps to have someone show you the best practices and how to(s) for a technology allowing you to focus on what makes your solution unique to your company’s business. Copying sample code and reusing libraries and frameworks also saves time that can be used to work on other development projects.



Improved Quality

One of the best measures of developer program membership, according to developers in the recent Evans Data Developer Relations Program survey, is the improvement in the quality of their code. We know that developers write code. At the same time, developers also read code. Being a part of a developer program allows developers to avoid worst practices, talk with other developers about how to performance tune code, find and create workarounds for issues, write unit and system tests, use audits and metrics tools to identify code smells, and more. Hearing about development problems and solutions from other developers in community forums, in articles and on webinars helps another developer avoid the same problems, traps and pitfalls. Being able to access a bug tracking database on  a developer program site will lead to better quality products being built by your customers and your own R&D teams.



Additional Benefits Heard from your Community Members?

Do you have additional developer benefits that you’ve heard from your developer community members? Send me an email with your list.

David I Facebook Avatar

David Intersimone “David I”
Vice President of Developer Communities
Evans Data Corporation
Skype: davidi99
Twitter: @davidi99


Developer Relations Best Practices and Tools of the Trade – Webinar Info and Links

As part of my DevRelate webinar presentation, “Developer Relations Best Practices and Tools of the Trade“, I am providing the links to the tools, websites, bloggers and other resources that I used for each of the seven best practices I cover in this week’s webinar. As I mention in the webinar, Evans’s Data Tactical Marketing – Developer Marketing and Developer Relations Programs – developer research reports provide hundreds of best practices that could have covered. Since I have to start somewhere, I’ve started with seven. My plan is to cover additional best practices and tools in future DevRelate webinars. Stay tuned to the DevRelate blog for news about additional webinars, dates and times.

Evans Data Tactical Marketing Reports

You can find the table of contents and a few sample pages from each report on the pages linked below. Contact our salesx team if you want to purchase the reports. The release schedule for all of our 2017 research reports can be found at


Seven Best Practices

Seven Best Practices Covered in this week’s Webinar

  • Social Media
  • Blogs
  • Newsletters
  • Webinars
  • Videos
  • Documentation
  • Answers


Social Media

Blogging tools:


  • The Art of Social Media, Power Tips for Power Users – Guy Kawasaki and Peg Fitzpatrick –




Blogs for developers and DevRel professionals (you should also follow and collaborate with):

Thought/Tech leader blogs:


Platform/Language blogs:


News/Press blogs/articles:


  • Word Press Newsletter Plugin – free plugin to add newsletter features to your WordPress based site or blog. Integrates with WordPress standard login form.
  • Newsletter Archive Plugin Extension – adds a smart tag that you can put on a page to create and update when you create new newsletters.
  • Oracle Eloqua – cloud based marketing automation driving dynamic journeys.
  • Marketo – marketing automation for companies of any size.




  • MediaWiki – open source wiki project written in PHP. Used by Wikipedia and Wikimedia. You can use the Book Creator extension to select Wiki pages and create a book. You can use the Collection extension to create collections of Wiki pages and export them as a PDF or a book. You can take your collections and have a book printed on demand by PediaPress.
  • Calibre – free, open source e-book management tool for creating and converting content for eBooks. You can create and edit eBooks for major eBook formats. It also has a feature to synchronize eBooks to book reading devices.



Email me if you need additional help, links, tools, info

You can find additional tools and links that I use on my earlier blog post, “Developer Relations Tools of the Trade“. I will keep updating this blog post throughout the week. If you have tools, links and other resources to add, send me an email.

David I Facebook Avatar

David Intersimone “David I”
Vice President of Developer Communities
Evans Data Corporation
Skype: davidi99
Twitter: @davidi99



DevRelate Webinar Jan 24,25,26: Developer Relations Best Practices and Tools of the Trade

Some of the most crucial elements of a successful developer program surround the awareness, acquisition, and retention of your developers. You have to provide tools, technical information, SDKs, support and create a community website that encourages participation amongst developers in forums, blogs, hackathons, contests and training events through targeted outreach.

It might sound like a tall order but there are methods, techniques, and insights that apply to every program and the tactics used to reach developers that can only come from years of research and experience.

Join us for the “Developer Relations Best Practices and Tools of the Trade” webinar on Jan 24, 25 & 26 – Reserve Your Seat Today!

This DevRelate webinar highlights several developer relations best practices and “tools of the trade” used to facilitate and automate outreach to developers. During the webinar, David I will demonstrate several useful tools and services that he uses to reach out to DevRelate members and developers. This developer relations best practices and tooling webinar content is supported by Evans Data Tactical Developer Marketing (Developer Marketing Patterns and Developer Relations Programs) research results.


1) Introduction to Evans Data Developer Marketing Research
2) Developer Relations Best Practices
3) Demonstrations: DevRel Tools of the Trade
4) Q&A

Dates and Times

This webinar is offered six times on January 24 and January 26. Select the date and time that works best for you. Use the pull down date/time box on the GoToWebinar registration page to select the session you want to attend. Register here!

Tuesday (Jan 24)

  • 7am Pacific Time (9am CST, 10am EST, 3pm GMT, 4pm CET)
  • 10am Pacific Time (12pm CST, 1pm EST, 6pm GMT, 7pm CET)
  • 1pm Pacific Time (3pm CST, 4pm EST, 9PM GMT, 10pm CET, 8am Sydney AEDT Jan 25)


Wednesday (Jan 25)

  • 4:30pm Pacific Time (6:30pm CST, 7:30pm EST, 12:30am GMT, 1:30am CET, 8:30am Beijing CST Jan 26, 11:30am Sydney AEDT Jan 26)


Thursday (Jan 26)

  • 7am Pacific Time (9am CST, 10am EST, 3pm GMT, 4pm CET)
  • 10am Pacific Time (12pm CST, 1pm EST, 6pm GMT, 7pm CET)



David Intersimone “David I”, Vice President of Developer Communities, Evans Data Corporation

Who Should Attend

  • Managers & Directors of Developer Programs
  • Technology & Developer Evangelists
  • Business Development Managers & Directors
  • Product Marketing Managers & Directors
  • Marketing Managers
  • Corporate Communications Managers
  • Heads of Developer Marketing
  • ANYONE who deals with developers!

The insights provided in this webinar stem from years of experience and the direct input from a global panel of software developers about what works for them and what doesn’t.

Whether you are starting a new developer relations program or enhancing a current one, you deserve all of the help you can get! Register Now!


Does your DevRel Program provide “Hero App” template projects?

In marketing our developer focused products, frameworks and services, we often create screen shots, sometimes called the “hero” shot, that provides high level visualizations of the product, frameworks and services and what developers can potentially build. When I visit developer relations program sites, I find lists of SDKs, APIs, tutorials, demos, documentation, videos, white papers, etc. What I seldom find are complete MVP (minimally viable product) or DevRel Hero App template projects for developers.

Hero App Screen Shot

It’s great to see all of the sample projects for each API, these are great for learning the specific calls, parameters and return results. In the early days of Java Enterprise Edition (when it was still part of Sun Microsystems), you could find the Java Pet Store project. The Petstore project gave you the complete solution for an AJAX enabled web application. You could load the project and experiment with you. You could use it as a starting point for your own Java Enterprise web applications. Java Petstore was part of Sun’s BluePrints program: “The Java BluePrints Program program helps developers create robust, scalable, and portable applications by providing guidelines, patterns, and code that illustrate best practices on how to build end-to-end applications using Java technology.”

DevRel Hero App

Examples of DevRel Hero App Template Projects

Here are a few examples of template and complete sample applications provided by developer relations programs. You can also search on your favorite developer platform or service sites and look for application templates, sample projects, and showcase applications.

Microsoft Visual Studio Templates for Web Projects – “Visual Studio includes project templates to help you get started when you create a web project. You can create web application projects or web site projects. By considering the most appropriate project type before you begin, you can save time when you create, test, and deploy the web project.”

DNN Software DNN (formerly known as DotNetNuke) : CMS open source platform for .NET – “DNN Platform is a free, open source .NET CMS and the foundation of DNN’s Evoq product offerings. Over 750,000 organizations worldwide have built websites powered by DNN Platform.”

Google Android XYZTouristAttractions Sample – “This sample aims to be as close to a real world example of a mobile and Wear app combination as possible. It has a more refined design and also provides a practical example of how a mobile app would interact and communicate with its wear counterpart.”

Oracle Jet WorkBetter App – “WorkBetter is a complete sample app showcasing the capabilities of JET for building web applications. WorkBetter has been designed for use as a web application in browsers from a mobile phone up to desktop. WorkBetter demonstrates web UI patterns and best practices, including Routing, ojModule, and data resource interactions.”

Facebook F8 2016 Developer Conference App – this is “the source code of the official F8 app of 2016, powered by React Native and other Facebook open source projects”. It includes sub-projects for iOS and Android apps that were available in the Apple AppStore and Google Play. “We’ve created a series of tutorials at that explain how we built the app, and that dive into how we used React Native, Redux, Relay, GraphQL, and more.”

DevRel Hero App


Do you have DevRel Hero App Template Projects?

If you have Hero App template projects as part of your developer relations project that highlight complete solutions, please email me.

David I Facebook Avatar

David Intersimone “David I”
Vice President of Developer Communities
Evans Data Corporation
Skype: davidi99
Twitter: @davidi99



OK, Code is King! But, where should you put your Developer Relations sample programs?

All developers require a Developer Relations Programs to follow the “3 C’s” – Community, Code and Content. To this list of C’s I also add a few of my own: Collaboration, Continuity, Cooperation, Communication, Caring, Celebration, Civility, Consideration, Clarity, Conversation and Curiosity. In surveys, during conversations, in emails and as the most commonly asked webinar question, developers tell us that Code is King! Even though we provide documentation for SDKs, APIs, libraries, frameworks, systems and applications, the ultimate documentation is the source code itself. The Computer History Museum (CHM) collects the source code for great computer software programs and systems. Do you want to download the source code for MacPaint and QuickDraw created by Bill Atkinson? You can download them both and you can read the story behind the software too! I love what CHM is doing to preserve the source code artifacts of our industry’s history. Developers tell Evans Data that source code examples, sample projects and tutorials are some of the top requirements for a successful developer relations program. So, the question is, where should you put your sample programs so that your developer relations program members can find it, download it and use it?

Developer Relations – where to put your sample programs, tutorials and source code?

There are several places that Developer Relations programs put there source code. Some programs keep their code on their own servers (ftp or http access), some put code in public repositories and others put their source on code hosting sites. There are many sites to choose from including: Amazon S3, Microsoft Azure StorageGitHubSourceForge, DropBoxCloud Forge, BoxCodePlex, Google DriveAssemblaBitBucket, ProjectLocker, and LaunchPad. Most of these sites support the leading source code version control services including Subversion, Git and Mercurial. Some of the hosting sites will also provide additional tools and services like defect tracking, deploy/install, security scanning, and license compliance audits. Several of these sites are popular places to put open source software projects allowing the developer community to collaborate and enhance the sample code. Some of the sites also provide APIs (GitHub Developer for example) for you to automate interactions, search catalogs of entries, access control, and more. Other developer programs place source code on sites to make it simple to distribute and update the code. Most integrated development environments and programmer’s editors support pulling sample code from repositories.

Sample Programs

Where do you put your Developer Relations program and products sample code?

Send me an email and tell me where you put your developer relations program code.

David Intersimone “David I”
Vice President of Developer Communities
Evans Data Corporation
Skype: davidi99
Twitter: @davidi99


Developer Relations: Giving a Great Developer Tech Session

I have given thousands of presentations to tens of thousands of developers in person and online webinars. It’s been great to be able to create and present a broad range of technical sessions, keynotes, webinars, hands on labs, briefings, etc. It’s also an honor and a privilege to talk and listen to developers while showing them new technologies, architectures, methodologies, compilers, frameworks, libraries and tools. One of the most important things that we can do in our developer relations programs is to help educate our members. Meeting and geeking with developers is always a shared experience for me as I learn as much from developers as I present to them. Sometimes I have the luxury of attending developer conferences and meetups and learn new, cool tech from other developers. What makes a great tech session? What do developers want to see and hear from a developer relations evangelist? Here are a few of the Developer Tech Session best practices, observations and ideas that I’ve learned over more than 30 years as an evangelist.

Giving a Great Developer Tech Session

Developers have told me what they look forward in a technical session. Developers are not shy or quiet. They will also tell me when one of my presentations didn’t live up to their expectations or doesn’t cover the topic.

  1. Have a clear session title, description, agenda, timing, prerequisites, use cases, expected audience (who should attend) and expected session outcomes (what they’ll see, learn and walk away with). Ensuring that the session information is clear and focused will set the stage for a satisfied developer audience. Of course there will always be a few developers who won’t read the session information in advance of your presentation.
  2. Developers want to learn cutting edge methods, technologies, architectures and best practices. Make sure that your presentation is as technically exciting and interesting to you as it will be for your audience. It’s always fun to be able to show cool products, cool technology and cool demos.
  3. Have more source code than slides. Developers love to look at code and dislike slides. My good friend Charlie Calvert would refuse to use a slide application and would instead put bullet points, images and notes on HTML pages and use a browser for the non-source code parts of his presentations. If you need to have a couple of slides, try to keep them to a minimum: title slide, agenda slide, an architecture slide or two and a final Q&A slide with your contact, short URL to your a blog post for your presentation and source code download information.
  4. For source code, make sure your development environment or programmer’s editor has a large clear font. For source code I use Lucida Console font with 14 point size (or higher if you are presenting in a larger room). If you are using an IDE also configure it with a “Source Code Only” layout option. If you are giving a webinar, use 1920×1080 screen resolution (your developer audience will have multiple high resolution monitors on their desktops). If you are giving a live presentation, know the size of the room, display your desktop with code and walk to the far reaches of the room to see if you can read the font.
  5. Prepare and practice, practice, practice for your developer technology presentation. Doing this will help you avoid some of the challenging demo issues, configuration settings and timing problems for your session. There is always the possibility that you will be hit by the “demo beast” and have to remark “that’s never happened before”. A mysterious bug or crash will also have happened to every developer attendee in the audience. Problems, hopefully only one, will show that you are human.
  6. Developers love to see and listen to a dynamic presenter. This doesn’t mean that you should run around the stage, crack jokes, rant, rave, wear goofy hats, etc unless they are relevant to your presentation. Your audience audience will enjoy your session when they see that you are really excited about the topic, technology, tools, projects, source code and techniques.
  7. Arrive early for your presentation, check the setup and configuration (especially if you have multiple computers, servers, devices and internet connections) and make one last pass through the slides and demos before you start your presentation. It’s always good to make sure that something didn’t change since the last night. Remind yourself to talk clearly, loud enough for the room and slowly (especially if audience members don’t speak the same human language as you, thankfully all programming languages and most libraries/frameworks have English keywords and function names). If you have consumed too much coffee, Red Bull, Mountain Dew Code Red, 5 hour energy drinks and other high octane beverages, take care to not over rev during your presentation.
  8. Turn off all of your popups, notifications, Skype, emails, alarms, screen savers, sleep/hibernate modes and other operating system and apps that will disrupt your presentation. Developers don’t want to read all of your instant messages, calendar alerts, etc. You probably don’t want them to see confidential information, meeting reminders, messages from your family either.
  9. Control the audience during your presentation. Don’t allow some attendees to take you and the audience off topic (they can come up afterwards to ask their specific questions). It’s okay to take some questions along the way, especially if your presentation has logical transition points. If you are going to cover a topic later in the presentation, gently reply to a questioner that patience is a virtue and what they are asking for is coming up soon in the presentation.
  10. Did I mention to show lots of source code? You can never explain the source code enough to a developer. It’s okay to type in code during your presentation. That’s what we as developers spend a lot of our time doing. This also helps the audience follow along and kibitz with you on typos and alternatives. I believe that it is also acceptable to open prebuilt projects as long as you explain the project and walk developers through the source code. It’s also okay to have snippets of code ready in a notepad, especially for some longer and complex code sections I doubt that they whole audience will sit there and watch you type in thousands of lines of code.

A Few Final Bits of Advice

If you are going to use some slides and other visuals here are a few additional bits of advice.

  1. Take care with your color sections for fonts. Some audience members may have a color vision deficiency for red, green or blue. I had presenter training early in my evangelism career and was introduced to Mr. “Roy G Biv” (Red, Orange, Yellow, Green, Blue, Indigo, Violet). For text color selections choose one from Roy and one from Biv. Green, Black, White and 50 shades of grey are okay to mix in.
  2. If you need to include Slides in your technical presentation – you should read Guy Kawasaki’s “10/20/30 Rule for Powerpoint“. Visuals can convey so much more that text for most slides. If you have to have bullet points with words, try to use the 4×4 rule – 4 bullet points with 4 words max each.
  3. Have a blog post availalble in advance for every presentation you give. Make sure there is an easy to remember ShortURL for your blog post. With the blog post you can provide links to additional information, resources, sample code and some of the questions asked during your session. You can always update the information omn the blog post for days, weeks and years after the presentation takes place.
  4. Give the audience your contact information including email address, twitter handle, SkypeID and blog URL. If you take the time to present and your audience takes the time to attend, you will be just at the first step in a mutually beneficial relationship.

Do you have other Technical Presentation advice?

Being a developer relations evangelist or team member is a great thig. We are on this software development and technology journey together. I love getting your presenter and attendee ideas and feedback.

HippyDavidI davidi_tiedye_sm_180x180 David I in Polo colored Guy-Kawasaki-03

SkypeID: davidi99

Twitter: @davidi99