Developer Outreach and Marketing

On first look, software developers appear to be a more distinct and well-defined market segment than most others, which should make it easier to market to them. It’s always simpler to create messaging and positioning for a target market that is uniform and cohesive than it is for a very diverse market. And so developers give the appearance of being easy to market to.

After all, there are important primary characteristics that set developers apart from the general population. They write programs professionally, and as a result a very particular type of mental acuity and skill set is more likely to be found among this group than the general population. The very act of programming requires certain characteristics. The successful developer is logical, has a keen eye for detail, and responds to mental challenges with a kind of inquisitiveness that can be associated with analytical and creative mindsets. Developers are usually more cerebral, curious and way more literal than others.

However, while there is a measure of homogeneity amongst developers that can aid marketing professionals who are trying to reach and persuade them, there is also a level of divergence from the general population that makes developer focused marketing unique. Developers frequent and place confidence in different media than the general public; they appreciate different forms of touch, and different elements in messages are more likely to resonate with them. In addition, there is not just one form of development and the types of development this group of people engage in can be so diverse that reaching out to them requires a special understanding of what they do, in addition to an understanding of who they are and what media they trust.

You can do research to find out the specifics of today’s developer and we do. We can tell you lots of data that can aid in your development of a marketing campaign and strategy. For example, developers answer to a variety of titles in their jobs, the most common being programmer, development manager, or project lead, though titles vary considerably by company size. They are overwhelmingly male. Although the female contingent is growing, males still comprise at least three out of every four developers – the ratio varies according to geography, but both mean and women developers think there should be more women involved.

Their median age is 36 in most places in the world. They tend to be married, and to have one or two children. The typical developer has between three and 10 years of experience, and has a high-level academic degree — a bachelor’s degree or higher — though there many developers who continue to learn on the job in order to keep up with the ever changing technology.

These are valuable fundamentals on which to build a strategy, but you still need the insights that only experience in marketing to developers can bring.

Providing that insight and understanding for marketing success is what motivates us at Evans Data to host our annual Developer Marketing Summit. This year it’s on September 17 and 18 in San Jose. We’ve got two full days filled with insights, networking and knowledge headed by the top developer marketing professionals from virtually all of the major players in the industry. Intel, Amazon, Microsoft, Facebook, Salesforce, and many more will provide powerful insights into how to successfully reach and motivate software developers. Don’t miss this very important event.

Evans Data Developer Relations Conference 2017 Recap – Ignite talks

I had a great time meeting with all of our great attendees at the 13th Annual Evans Data Developer Relations Conference, March 27 and 28 in Palo Alto. To end the conference, several of us presented Ignite talks pitching our developer relations programs and technologies we use. If you don’t know about Ignite talks you can find additional information on the Ignite talk web site. Basically, an Ignite talk is a five minute talk using twenty slides that are automatically advanced every fifteen seconds. Normally ignite talks are presented about a wide range of topics, but an Ignite evening can also have a theme. I had four brave souls that volunteered to pitch their developer relations program this year.

Ignite Talk

The Ignite Presenters

I kicked off the session by pitching the Evans Data DevRelate Community and Academy for Developer Relations Professionals. Felix Sargent, Director of Developer Relations from Media Math, followed me and presented how MediaMath uses Swagger to ensure that their APIs “don’t suck”. Jayson Delancy, Developer Evangelist for Industrial IoT from GE Digital, presented how their developer relations program is measured and how they reach out to developers. Hannes Kuehnemund, Senior Product Manager from SUSE, gave his presentation about who and what is SUSE, their open source developer history and the push to encourage more application developers to participate. Finally, Andy Jiang, Developer Propaganda from Segment, started his presentation with a blank slide saying that they currently don’t have a public developer outreach program but are working on one and then went on to show how developers can use Segment’s solutions to help companies collect, unify, and act on their data.

The Audience Votes with their Applause

All four attendee presenters did a fabulous job in their presentations. At the end of the talks, the audience was asked to applaud for their favorite Ignite talk. I used the NIOSH Sound Level Meter App smartphone app from the US Centers for Disease Control (CDC). NOISH stands for the National Institute for Occupational Safety and Health. The app allows you to measure noise in your environment giving you an instant reading as sell as recording the peak level.

The final audience applause sound meter result picked Felix Sargent from Media Math as the winner. Congratulations to everyone who took part.
David I Facebook Avatar

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

Most Everything I learned about presenting I learned from Jerry Weissman

We just completed the 13th Annual Evans Data Developer Relations Conference which was held in Palo Alto California on March 27 and 28 (the Boot Camp took place on Sunday March 26th). As I was watching some of the presenters and their presentations, I was thinking back to the early presentation training I received from Jerry Weissman. I love sitting in on other speaker presentations. I know there is always something new I can learn about speaking in front of an audience including tips, techniques, slides and demos. While we were doing our conference retrospective meeting back in the office, I was thinking about what more I can do to help Developer Relations professionals and decided to pull together some of what I learned from Jerry and other presenters over my many years of presentations, panel discussions, webinars, product launches, and meetups.

Beyond the title of this article, here are see some of my thoughts about what I’ve learned by giving presentations, what I’ve seen in watching other presenters, and the days I spent, years ago, with Jerry Weissman. The only other piece of advice I have is to practice and present as often as you can – if you want to add presenting to your skills inventory.

Power Presentations, Ltd.: Corporate Presentation Training – Jerry Weissman

About Jerry: “Jerry Weissman is the world’s number one corporate presentations coach. His private client list reads like a who’s who of the world’s best companies, including the top brass at Yahoo!, Intel, Intuit, Cisco Systems, Microsoft, Dolby Labs and many others.” Read more about Jerry and his company –

Jerry Weisman

You should definitely Buy and Read his book: Presenting to Win: The Art of Telling Your Story, Updated and Expanded Edition

Jerry’s top words of wisdom about your presentation: “The key building block for Audience Advocacy is WIIFY — What’s In It For You. The WIIFY is the audience benefit. In any presentation, before you make any statement about yourself or your company, or the products and services you offer, ask yourself, What’s the WIIFY? What benefit does this offer my listener?”


Presenting to a Live Audience or Meeting

Here are the three aspects for giving a great presentation that includes slides/visuals. Doing live demonstrations or products and technologies adds several additional levels of training, setup, practice and especially how to handle “exception” cases when the demos don’t go very well.


1) E.R.A.

  • Eye Contact – keep your eyes on the audience, not on the floor, sky, etc. Look around the audience – front, left, right, middle, back. Move about the stage or front of the room – but don’t make quick moves like some comedians do, and don’t pace. Pretend that you are speaking one on one – in those conversations you usually look in the other person’s eyes when you are speaking with them. Do the same with your audience.
  • Reach Out – engage the audience with your hands, person. This advice comes from the days of the Knights with the handshake. A Knight meeting another Knight, would reach out their hand to show that they didn’t have a weapon. Reaching out to the audience will bring them in, show that you are open to them. If you feel comfortable, you can even go out in to the audience or move about the room. One time I started my talk while sitting in the audience with attendees and then moved around before I got to the front of the room. A couple other bits of advice for reaching out to the audience:
    • Avoid using a podium. While you need something to put your computer on – use a table, or stand for the computer. Speakers hide behind the podium, use it as a crutch, grab on to it. This means that you are putting barriers between you and your audience.
    • Use a remote control to advance your slides. This way you are separated from the computer and engaged more with the audience. Even better would be to have someone advance your slides – this way you don’t have anything in your hands that you might fiddle with. If you don’t have someone to advance your slides you can always combine moving to get some water and hit the spacebar on your computer and then move away.
    • Avoid putting your hands in your pockets – this could alarm the audience that you are going for a weapon, or keep you from reaching out. If you feel compelled to fidget with your hands – do it behind your back for a moment.
  • Animate – be animated but not crazy. It’s okay to nod your head, move your hands/arms around – not waving wildly – shake your head and shoulders. Don’t stand stiff even if you are petrified during a talk. Moving about will help you relax and also support having eye contact with a larger audience/room and also is part of your reaching out to the audience.


2) Avoid the Um(s), Ah(s), And(s), So(s), You Know(s), Stutter Starts/Restarts, etc.


  • Presenters sometimes feel that they always need to be talking doing a presentation. We feel compelled to be speaking, outputting audio even when moving between thoughts, bullet points, etc. Unconsciously many of us will use the Um(s), Ah(s) and such – often without realizing it. A better approach is to pause and rest your voice for a moment – this also lets the audience take a rest (they need it too). The only real way to fix this (if you have a bad case of them) is to record yourself giving a presentation for about 10-15 minutes at least. Play it back and watch and listen to yourself to count how many times you hear yourself with the Um(s) and Aw(s). As someone who edits presentations and webinars to create replays, I can tell you that I will usually remove 3-5 minutes of them in a 30 minute presentation. I still have this problem, using during Q&A time.
  • Let the audience read a quote – and you read along with them quietly at a “normal” reading pace. Instead of reading a quote that is already on your slide and the screens. The audience will be reading the quote while you are reciting it anyway. Let them. After you and they have read the quote, then you can talk about why you put the quote on the screen. IF your slide has a video with audio – you usually wouldn’t talk over the audio – why talk while everyone is reading?
  • Stutter Starts/Restarts – here I am not talking about stuttering. I’m talking about the starting a thought, stopping, starting the thought again, stopping, changing your starting thought. My advice is to put a slide up or listen to a question being asked and think a bit before you start talking. Again, the audience is still probably taking in the Slide, the question, the image. It’s okay for a few seconds to make sure you have your thoughts together and then talk. This can also happen to some presenters when you are trying to think and speak at the same time. Practicing your presentation, reviewing your slides multiple times before a presentation will help you feel that you can talk without starting, stopping, restarting. Allowing yourself to think on your feet and then speak will also allow the audience to think.


3) Mr. Roy G. Biv – Creating your presentation

3a) Colors – know the color spectrum and what colors work well with others. Take a look at the following and be reminded of our dear old friend: Roy G. Biv. Who is Roy? No one but it serves to remind us of what colors to combine in your presentations. Of course there are variations of colors beyond the specific rainbow and spectrum – Red, Light Red, Pink, etc.

ROY G BIV + White, Shades of Grey and Black – the Chinese restaurant menu of choices.

Choose one from column A:

  • Red
  • Orange
  • Yellow

Choose one from column B:

  • Green – works with just about everything

Choose one from column C:

  • Blue
  • Indigo
  • Violet

Have you noticed how well Yellow on a Blue background looks good? Adding drop shadows can also increase the clarity. You can use White, Black and shades of Grey with your choices.

3b) Color challenged attendees – the challenges related to how the eye is constructed and works – think Rods and Cones. The fact that some humans have eye conditions that might steer you to avoid certain colors or color combinations because of color blindness and other color based sight impairments. There are different types or color categories for color blindness:

  • Red Green color blindness – the most common type of color blindness – three conditions: Protanomaly (1 % of males) – Red, Orange and Yellow can appear greener. Protonopia (1 % of males) – red appears black. Shades of orange, yellow and green appear as yellow. Deuteranomaly (5 % of males) – yellow and green can appear redder, can be difficult to distinguish between violet and blue. Deuteranopia (1 % of males) – red looks brownish yellow, green looks beige.
  • Blue Yellow color blindness – rarer than red green – two conditions: Tritanomaly (extremely rare) – Blue appears greener and it can be difficult to tell yellow and red from pink. Tritanopia (extremely rare) – blue appears greener, yellow appears violet or light grey
  • Complete color blindness – most rare. Two forms: Cone Monochromacy – trouble distinguishing colors. Rod Monochromacy or achromatopsia – everything is black, white and grey.

3c) Resources for additional reading in this area


Other Presenter and Presentation Aspects to Consider

There are many other aspects for building and giving a great presentation. This blog post could go on for ever. Of course, as a presenter, you should be yourself, smile, exude enthusiasm, be confident, consider making startling statements, and more. For your slide show here are a few bits of advice that I review from time to time.


Room/Environmental Advice

  1. Room temperature – depending on the room size, you may have to deal with cold or hot rooms. What should you do? Remember first that the audience will also feel the same effects of the room temperature and humidity. If you have control over the environment, have the hotel, convention center or team set the room temperature as if it has bodies in it. If you can’t control the environmental aspects – then you (and your audience) can follow the same advice we give each other about wearing layers that you can take off and put on throughout the presentation.
  2. Sound System, Speakers noise, buzzing, hum – get to the room early (if you can) and check out the audio system (do a sound check) if there is one. If there is a nasty background noise in the audio system – have the AV team fix the problem before you start. No one likes to hear buzzing, static or hum while you are presenting. It is a major distraction. If your presentation has audio in it – make sure you have the right connectors and sound levels. Alert the A/V team as far in advance that you have special requirements for your computer, audio, power, device, etc. setup. Again, get into your room early to make sure you have all that you need. Don’t assume connectors or adapters. If you are going to be presenting a lot, bring what you need.
  3. Video Connectors – depending on your computer, notebook, and device – bring connectors, adapters and cables to connect to the projector or large monitor. My MacBook Pro has HDMI output. This is the norm today for most “modern” projectors and monitors. But, just in case, I also bring adapters for VGA and DVI just in case.
  4. Internet Connection – Most places have Internet access. But sometimes the quality of the Internet signal or speed is less than what you need. Sometimes you will need some ports opened that are blocked in the location you are presenting. I have a second mobile phone that I can set up as a Hot Spot to give me a better quality and open ports. For example, I use Airplay to display the screen of my iPhone on my Mac connected to a projector/monitor. Airplay requires some ports that are often blocked. The only ways around this are to ask that an Airplay set of ports be opened (good luck) or to use an alternate Internet connection – hot spot to the rescue. The second benefit of using a phone as a Hot Spot is to avoid being caught up in bad internet speed in a hotel or convention center, or too many other devices connected to the same Wi-Fi or wired network.
  5. Your Cell Phone – set it to “Do Not Disturb” or completely off. Put it away from the sound system to avoid interference, buzzing and other distractions. Do not have it in your pocket or attached to your belt. Unless it is part of your demo, tell anyone who might message or call that you are giving a presentation during a specific date/time and won’t be monitoring your phone.
  6. Fluids – If you are going to keep hydrated, drink still water that is room temperature. No Ice Water – constricts the vocal cords? Avoid too much coffee, never drink alcohol before, during or after a presentation (unless it is in the evening after all of your sessions are completed), Red Bull, 5-Hour Energy, chocolate/sugar, etc. Be naturally amped up for your audience. Get a good night’s sleep the night before and hydrate, hydrate, hydrate (ok, watch your total fluid intake so that you won’t need to take an unplanned break in the middle of your presentation).
  7. Floor monitors for video and audio – For a larger room/convention center – have a floor monitor (or 2 or 3 if it is a large stage and large audience) between you, stage and the audience. If there isn’t room or separate monitor available, it’s okay to turn look at a slide and refer to it. It’s also good to have audio monitor speakers between you and the audience (if possible) – then you won’t have to ask the audience if they can hear you. You can hear what the audience is hearing.
  8. Audio Feedback and Projector Blindness – avoid getting near the PA system speakers. The audience doesn’t want to hear a 60’s Jimi Hendrix guitar/amp feedback. If the projector is not behind the screen or raised above your head, now where the beam is and avoid standing between the projector and the screen. Don’t go near the light “Carol Anne” – you’ll have spots in your eyes for a while.
  9. Lighting – Don’t have bright lights shine on the screen that your presentation is being projected on. The lights will wash out your slides. While you don’t want to have complete dark in the room, you can usually play with the room pre-sets to get lights off the screen. If you can’t control the lights yourself, you can ask the hotel or convention center to set up a preset for your room. One other option would be to move your screen and projector to another part of the room where the ceiling lights won’t affect the quality of your slides.


Practice, Practice, Practice

  1. Practice in the mirror and on camera. I know that it is hard to watch yourself on video, but it is important to take an honest look at yourself. Count the number of um(s), ah(s), bobbles, times not looking into the camera, etc. Think about what you see in regards to what you have read above and also what you are trying to accomplish in your presentation. How does it look and sound to you?
  2. If you’re the kind of person that can’t practice to a camera, to an empty room or in front of a mirror, practice in front of your family, office mates, or a picture of a group of people.
  3. Rinse and Repeat – make any changes/adjustments. Record yourself again. Do you see improvements? Do you have less um(s), ah(s), not look at and reaching out to the camera and animating? Repeat as often as necessary.


Give lots of Presentations of Different Types/Kinds

Variety is the Spice of Life! Once you are ready, give lots of presentations or all types, topics and lengths. Solicit and read (if there are speaker evaluation forms) all of comments after your presentations. Take all of the comments and suggestions to heart. Remember also, that there might always be one or a few outlier evaluators in your audience that don’t like you, don’t like your presentation, and don’t like anything. It is okay to try and learn a nugget from these attendees, but don’t let that color all of the other feedback.


Good Luck (So Long) and Thanks for All the Fish!

I wish you all good luck in all of your future presentations. I hope that all of your presentations will be warmly received. While you might have a less than stellar presentation from time to time, you can always learn from missteps and get more comfortable and professional as a presenter every time you get in front of an audience.

Do You have your own Presentation Tips and Experiences?

Send me an email if you have your own presentation best practices or links to your favorite presenter advice articles.

David I Facebook Avatar

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


Developer Relations Program Spotlight: Uber

Each Developer Relations Program Spotlight blog post highlights the many aspects of a company’s developer outreach activities. Included in a spotlight is some background information about the program, one or more program team members, a question/answer about the features and benefits of the program and an “At-a-Glance” checklist of top program offerings. This time I shine the spotlight on the Uber Developer Relations Program.

Adam Rogal

Head of Engineering, Developer Platform, Uber

adam rogal   Uber_Logobit_Digital_black

Fusing Developer Relations and Platform Engineering

At last year’s Evans Data Developer Relations Conference (2016), Adam gave a great presentation, “Going from 0 to 60 by fusing developer relations and platform engineering”, at the 2016 Evans Data Developer Relations Conference in Palo Alto. One of the unique aspects of the Uber developer program is that it fuses together developer relations and platform engineering inside one organization. Uber released their first API for developers in 2014.

Uber’s platform mission is “Build Moving Experiences”.

  • “Build” involves working with developers, forging partnerships and providing tools. The Uber cultural value is to “Let Builders Build”!
  • “Moving Experiences” results in products that bring job, getting people from A to B, provides features for people while they move, makes daily life easier and saving time and money. The Uber cultural value is to “Make Magic”!

Adam presented a slide with many well-known global brand name logos saying “Today, leading brands elevate their experience with Uber”. Adam went on to showcase some of Uber’s APIs and how developers are creating innovative applications that do more than just get the rider from point A to point B. He also gave some suggestions for additional value added features that companies and developers could add to enhance each trip.

At Uber engineering and developer advocacy are joined to integrate the platform, features and SDKs.

UberDrc2016Preso Figure 1

Adam highlighted the synergy of his team’s integration of developer relations and engineering with the phrase, “Enable magical moments through the API”. The closeness allows for features to be provided, developer feedback to come straight into engineering and SDK development to continue in real time.

Developer advocacy ensures that every developer is aware of the Uber API and that the platform direction is aligned with developer needs.

The bi-directional flow follows the following flows:

UberDrc2016Preso Figure 2UberDrc2016Preso Figure 3

You will find many of the Developer Relations Conference 2016 presentations on the DevRelate community at

This year, Adam is giving a keynote presentation at the 13th Annual Evans Data Developer Relations Conference, March 27-28 in Palo Alto California. “Evolution of a Developer Platform: An Inside-Out Journey”. Join this keynote session for an introspective look at the evolution of the Uber Developer Platform from its inception to today. Find out what worked, what didn’t and lessons learned along the way.

Bio: Adam Rogal is the head of engineering of Uber’s Developer Platform. Uber’s mission is a simple one – transportation as reliable as running water, everywhere, for everyone. Uber’s Developer Platform believes in that same principle, ensuring its APIs are available to everyone, everywhere. Preiously, Adam lead developer relations for publisher ads products at Google, enabling countless developers to monetize their passion, hobbies, and business.


Uber Spotlight Q&A

1. What are the benefits of having the developer evangelism and engineering teams in one organization and are there any negatives of work on more problems because of that alignmentWe experienced a variety of benefits from this model.

For one, the ownership dynamics change radically; Developer Advocacy is empowered to make improvements to products like the SDKs, Docs and Developer Tools. The feedback loop between external developers and the engineering teams is also dramatically tighter. Feedback and bug reports from the community get turned into actions and improvements quickly. Last but not least, it improves the culture of both teams since they learn from each other.

For instance, post-mortems are required for all support requests handled by Developer Advocates who answer two important questions to improve the developer experience: (1) what did we learn from this request? and (2) what was done to prevent a similar question in the future? On the other side, Engineering is more encouraged to think about the impact of their work on developers and make decisions to build the best possible experience for their customers.

2. Your talk showed how you uniquely combine engineering and developer relations into one team. How does your team integrate with other parts of Uber – development, sales, web, marketing, partner programs, etc.?

We operate as a true platform team, even internally. To do this, we provide services and technology substrates to internal Uber teams to use if and when they build products for developers. Just like an API, we have defined an interface and SLAs for interactions with internal teams. We help teams to understand the benefits of an external API and we provide guidance throughout the development journey of new APIs. We intend to ramp this up further with internal talks and advocacy programs as well.

3. How many developers are in the Uber developer program?

We have a few dozen people on the team. The platform powers thousands of companies using Uber’s API, ranging from multinational corporations to city transit planners to dorm-room startups.

4. How many applications have been created using the Uber SDKs/APIs?

Check out our showcases for examples of great integrations. We’re not necessarily looking for quantity so much as quality. We try to provide tools that encourage developers to think about the future and make creative leaps.

5. How has developer outreach positively impacted Uber’s business: revenue, customer satisfaction, partnerships, etc.? Can you share some statistics?

We broadly think of the Developer Platform as a way to enable third party developers to leverage Uber’s capabilities as a starting place for their own innovation and positive disruption. If we can help developers be successful with our tools then, as a contributor to that success, Uber benefits in innumerable ways.

6. Do you track any data about return on investment on the cost of doing developer relations and what it means to the Uber’s business?

Here at Uber, we like to have big bets. This means that we’re willing to take a longer-term-view on some of the activities we’re engaged in.

But, it’s important we have wins along the way. For example, when we go to events, we expect to onboard some new developers to our platform, which we measure by website visitors, new apps, and time to first sandbox and production call.

7. Did you have any challenges or issues in getting buy-in from Uber – to have the developer program number one and number two having it integrated as part of platform engineering

Our leaders strongly believe in the power of open developer ecosystems. They’ve been very supportive and have even encouraged us to think bigger.

8. Are there any other key performance indicators statistics that you track and provide to Uber management to keep them informed and supporting how the developer program is doing?

There are some short-term tactical numbers we pay attention to like Trips and Bookings. But there are also early indicators of longer-term success like our NPS and developer engagement.

9. Is there anything else that you’d like to add about the Uber program its uniqueness and where do you see developer relations and developer outreach going in the future?

We enable developers to, with just a few API calls, add a little bit of the real world into their virtual products. Bits to atoms..
The great developer platforms today all provide unique features during key moments in a user’s life. Amazon Echo or Google Home are with you at home. Facebook Messenger is there to help you chat with friends. Slack helps you collaborate with your colleagues. Uber is there with you while you travel from A to B. We believe there’s a lot of opportunity here for Developers of all sizes to elevate and differentiate their apps with features and trip context from Uber. We’re just at the beginning.

About the DevRelate Developer Relations Program Spotlights

In today’s interconnected world, companies in all industries need to publish APIs and cultivate a developer community to access and use them. To be competitive today, attracting and supporting developers is essential. The key to cultivating a vibrant developer community that uses your APIs and supports your platform is a good developer relations program.As part of the Evans Data DevRelate community, David I is creating a series of developer relations program spotlights highlighting companies that are reaching out to developers to achieve higher levels of business success. In collaboration with the leader of a company’s developer program, these spotlight articles will help advance developer program best practices, increase developer successes and enhance each company’s industry leadership.If you want to have David I create a developer spotlight article for your company, contact me at

Developer Relations Tools of the Trade

I’m often asked about the different tools I use in my developer relations, chief evangelist, developer communities and developer cheerleader jobs. This blog post contains a list of some of the tools that I currently use. It is not meant to be a complete list of all possible developer relations tools nor is the list an advertisement or endorsement of tools. There are many additional tools that are available for all aspects of being a developer relations professional. Where possible, I have included links to additional tools that are available.

Developer Relations Tools I Use

I’ve divided up the tools I use into several categories grouped by functionality and features. There are many other choices for tools you will use in your developer relations job, for your program, for developer outreach, developer program marketing, etc.

JeffGordon Nascar ToolBox Developer Relations Tools


Webinars, Meetings, Screencasts, Videos:

  • Online Webinars/Meetings/Conferences – GoToWebinar by Citrix (Windows, macOS, iOS/iPad), Facebook Live, YouTube Live. I’ve also used WebEx from time to time.
  • Screen Cast Capture, Editing and Rendering – Camtasia by TechSmith (Windows and macOS). My default settings for capturing, editing and rendering videos – MP4 format, 1920×1080 resolution, 3-5 fps for slides/code, 15-30 fps for full motion video/animations.
  • Broadcast video from my computer to multiple sites (Facebook Live, YouTube Live, Twitch and others) – Open Broadcaster Software (OBS)
  • Video Conversion – Miro Video Converter


Audio Editing/Enhancement:


Slides and Bitmaps


Social Media Management/Marketing Tools:



  • WordPress, Microsoft Word, LibreOffice, Windows Notepad




Social Sites (personal):


Social Sites (DevRelate):


Mind Mapping/Brainstorming:


Cloud Storage / FileSharing:


Alerts / Feeds / News:


Newsgroup Reader (NNTP protocol):

  • XanaNews (written in Embarcadero Delphi)


Developer Answers Sites:


Short URLs:

  • Bitly
  • Internal Evans Data app


Virtual Machine Software (for my MacBook Pro) for demos/appdev:

What Other Developer Relations Tools Do You Use

As I mentioned, the above is a list of the tools I use every day in my developer relations and evangelism job. If you use other tools, please send me an email with the other tools you use in your developer relations job.

David I.