Developer Relations Boot Camp 2015 Pillar V: Try New Things Drew Schweinfurth Lead Developer Evangelist, Walgreens 

Developer Relations Boot Camp 2015 Pillar V – Try New Things 24 hour Hack-a-thons: ➔  Technical Issues: ◆  You will see people trying things that you have never seen ◆  You will need tech backup to answer questions ➔  Communication: ◆  Clearly communicate via speeches ◆  Host Schedule / Updates on a static Page or Github Repo ➔  Entertainment: ◆  Beer and Pizza or Local foods and Local Craft Beer Online Hack-a-thons: (ex: challengepost.com) ➔  Technical Issues: ◆  Easier to manage as your whole team can be apart of the event ➔  Communication: ◆  Updates / Notices must go to every participant ◆  Send weekly checkup messages to help those struggling ➔  Entertainment: GIFS!! 

Developer Relations Boot Camp 2015 0% 5% 10% 15% 20% Percent of Programmers Support a particular tech/ community Learn about new tech or tool Discover entrepreneurial / partnership opportunities Exposure to peers, netw orking, social interaction To w in jobs, employment possibilities Which of the following BEST describes why you attended a hackathon? (Top 5 reasons) D evelo per  Marketing  2015,  ©  2015  E vans  D ata  C o rp. Top Reasons for Attending a Hackathon: Hackathons are a great way to bring together program supporters and inform them about your technologies 

Developer Relations Boot Camp 2015 Pillar V – Try New Things Informing Partners vs Spamming Partners ➔  Emails: ◆  These are easy to make and easy to send ◆  Using these too much can make people annoyed ◆  Writing a personal message is better than a generic template ➔  Phone Calls: ◆  Offers instant access to you and the third-party on both ends ◆  Offers more personal touch then an email could ever give ◆  Gives both parties the phone numbers for future contact 

Developer Relations Boot Camp 2015 0% 10% 20% 30% 40% Percent of Programmers Once per day or more Once per w eek or more Once every tw o w eeks or more Less than once every tw o w eeks Never How often do you take some kind of action as a result of reading something in an email newsletter? D evelo per  M arketing  2015,  ©  2015  E vans  D ata  C o rp. Efficacy of Newsletters Fifty-five percent of developers take action as a result of newsletters on at least a weekly basis. 

Developer Relations Boot Camp 2015 Pillar V – Try New Things Grow your ecosystem via Open Source: ➔  Stack Overflow is where most devs talk: ◆  You should have a presence there ◆  You should answer any questions about your API/SDK ➔  Github is where most devs share: ◆  You should have at least some sample code there ◆  Really easy to use and update, the community helps ➔  Basecamp is the bridge: ◆  Your business team and dev team ◆  The third-party business team/person and dev team/person ➔  Why use open source solutions?: ◆  Allow for “work-arounds” with large corporation issues ◆  Helps with cleaning up “global” opinion of the API/SDK ◆  Dev’s like seeing code that works right away! ◆  Getting your partners live, while maintaining quality of integrations 

Developer Relations Boot Camp 2015 0% 10% 20% 30% 40% Percent of Programmers Currently doing this Plan to w ithin 6 months Plan to w ithin 7 to 12 months Plan to after 12 months Have no plans What are your plans for developing software in a collaborative forge over the Internet (e.g., Sourceforge, Github)? D evelo per  R elatio ns  2015,  ©  2015  E vans  D ata  C o rp. Involvement in Collaborative Forges Nearly two-thirds of developers, currently develop on a collaborative forge, or include it in their six month plans 

Developer Relations Boot Camp 2015 Pillar V – Try New Things Worksheet ▪  Top 3-5 NEW THINGS to engage with your developer audience based on their partnership with and your goals. ▪  How do you choose to interact with different types of developers 

Developer Relations Boot Camp 2015 Pillar VI: Onboarding Developers Drew Schweinfurth Lead Developer Evangelist, Walgreens 

Developer Relations Boot Camp 2015 Pillar VI – Onboarding Process Our Best Practice 6 steps to Onboarding: ➔  The “Connection”: ◆  The first Email / Referral / Developer Page Hit ➔  The “Interest”: ◆  The form / page the user will use to get an API Key ➔  The “Approval”: ◆  This must auto-magically work immediately once they see it ➔  The “Documentation”: ◆  Should be able to master this in less than a minute ➔  The “Request”: ◆  The moment of pure euphoria after the 1st successful API call ➔  The “Call”: ◆  The phone call to provide the needful to finish the integration 

Developer Relations Boot Camp 2015 Pillar VI – Onboarding Process Integration or Bloatware: ➔  Format of your software: ◆  Which works, API or SDK or both? ➔  Required Assets: ◆  Which files are needed, how big are these files? ➔  Value of Integration: ◆  How does the app value from integrating? ➔  DIY Integration ◆  Have you ever tried using your own software? 

Developer Relations Boot Camp 2015 Pillar VI – Onboarding Process Worksheet ▪  What an onboarding process should look like! ▪  Show us a Sample Documentation you like.