Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Breaking Down Barriers to "Hello World"

393 views

Published on

For any developer, the faster you achieve “Time to First Hello World,” the better the overall experience. Whether you are a developer just learning how to code or have 10+ years of experience, the first “Hello World” with a new API, framework, or programming language is an amazing feeling. This benchmark becomes even more important for beginners. Along with less access to help, mentorship, and other resources, just getting started can be very challenging and potentially detrimental. If beginners can achieve small wins early on, an entire world of possible projects they can code on their own opens up.

In this talk, we will explore the barriers beginner (and experienced) developers face when getting started with a new API, framework, or programming language. We will also discuss strategies for better documentation, examples, and tutorials that break down these barriers and ensure success early on. Lastly, we will talk about why it is important and mutually beneficial to care about beginners using your API, framework, or programming language.

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Breaking Down Barriers to "Hello World"

  1. 1. BREAKING DOWN BARRIERS TO “HELLO WORLD”
  2. 2. Community Engineer at Keen IO taylor@keen.io @taylor_atx TAYLOR BARNETT
  3. 3. SHORT HISTORY OF “HELLO WORLD”
  4. 4. TRANSCENDS HISTORY
  5. 5. WHY IS IT IMPORTANT?
  6. 6. PUT SOFTWARE TO IMMEDIATE USE
  7. 7. EARLY WINS 🙌
  8. 8. BEGINNERS HAVE LESS ACCESS
  9. 9. BARRIERS
  10. 10. 😨 😨
  11. 11. 1. OVERWHELMING
  12. 12. “THAT’S IT.” “JUST READ THE SOURCE CODE.” “JUST READ THE MANUAL.”
  13. 13. 😅 IS OKAY, BUT 😓 IS NOT
  14. 14. 2. WASTED ENERGY
  15. 15. SUBLIME TEXT VS ATOM VISUAL STUDIO VS NETBEANS VS WEBSTORM ECLIPSE VS NETBEANS VS INTELLIJ PYCHARM VS SUBLIME TEXT VS ATOM
  16. 16. 3. BAD DOCS
  17. 17. 4. WORKING DEVELOPMENT ENVIRONMENT
  18. 18. STRATEGIES
  19. 19. FROM “SIX WAYS TO ACCELERATE TIME TO FIRST ‘HELLO WORLD’” 1. Make it clear what you do 2. Offer free or trial API access 3. Fast, automated setup 4. Clear, accurate documentation 5. Copious code samples 6. Provide tools
  20. 20. 1. BETTER DOCS
  21. 21. BETTER QUICKSTART GUIDES
  22. 22. BASICS FIRST
  23. 23. TWILIO
  24. 24. GITHUB
  25. 25. SPRING FRAMEWORK
  26. 26. WORD CHOICE
  27. 27. COMMON ERRORS
  28. 28. EXAMPLES
  29. 29. 2. MORE WORKING PROJECTS
  30. 30. AUTH0
  31. 31. MAKE IT EASY TO EDIT, DEPLOY, RUN
  32. 32. 3. MORE USER TESTING
  33. 33. 4. BETTER SUPPORT
  34. 34. CHAT EMAIL FORUM GITHUB STACKOVERFLOW
  35. 35. “Code is hard.”
  36. 36. Community Engineer at Keen IO taylor@keen.io @taylor_atx TAYLOR BARNETT

×