Optimizing for Developer Happiness

Transcript

1. Optimizing Developer Happiness @bdougieYO

2. ❤# @bdougieYO @bdougieYO おはようございます

3. ? @bdougieYO @bdougieYO

4. @bdougieYO

5. @bdougieYO

6. Beautiful San Francisco @bdougieYO

7. Beautiful San Francisco has a trash problem @bdougieYO

8. Beautiful San Francisco has a trash problem @bdougieYO

9. ? @bdougieYO Japan doesn’t have trash problem? @bdougieYO

10. There is hope! @bdougieYO @bdougieYO

11. @bdougieYO

12. None

13. @bdougieYO

14. Take care of your own mess! @bdougieYO

15. Gather up your things and ask… @bdougieYO

16. @bdougieYO

17. Does this spark joy? @bdougieYO

18. We should always be optimizing for this joy @bdougieYO

19. None

20. @bdougieYO @bdougieYO

21. GitHub provides a better way to collaborate @bdougieYO @bdougieYO

22. @bdougieYO @bdougieYO

23. Developer AdvocateTools Brian Douglas @bdougieYO @bdougie @bdougieYO

24. Queen Bey

25. What Would Bey Do? @bdougieYO

26. go to bat for the hive

27. Onboarding and keeping developers @bdougieYO @bdougieYO

28. Developers are on your site because they specifically sought out

    your product @bdougieYO @bdougieYO

29. https://betta.io/blog/2017/04/12/developer-experience-review-github/

30. 1. Messaging + First Touch 2. Speed to Success 3.

    Reference Projects/Materials/DevPortal/Docs Framework for developer happiness @bdougieYO @bdougieYO

31. Direct/Channel @bdougieYO @bdougieYO

32. 1. How easy to get an idea of what your

    product is? 2. How long does it take to go from 0 to using your product? 3. How easy is it for a developer find a references and examples? Let’s focus on these 3 questions @bdougieYO @bdougieYO

33. Messaging + First Touch 1. How easy to get an

    idea of what your product is?

34. Direct @bdougieYO @bdougieYO

35. The front door @bdougieYO @bdougieYO

36. What is GitHub? @bdougieYO @bdougieYO

37. A place to collaborate, host, and review code @bdougieYO @bdougieYO

38. Developer concern: What is this going cost me? @bdougieYO @bdougieYO

39. @bdougieYO @bdougieYO bit.ly/tastylicks

40. How much is GitHub? It’s free to start @bdougieYO @bdougieYO

41. GitHub’s channel @bdougieYO @bdougieYO

42. Guided first touch through the channel @bdougieYO @bdougieYO

43. (Channel) @bdougieYO @bdougieYO

44. Heroku @bdougieYO @bdougieYO

45. @bdougieYO @bdougieYO

46. @bdougieYO @bdougieYO

47. Programming language Frameworks Conferences Tutorials Partnership Open Source Channel @bdougieYO

    @bdougieYO

48. developer tools, need a channel @bdougieYO @bdougieYO

49. 1. Use descriptive copy 2. Encourage usage and return visitors

    3. Leverage the channel to qualify/teach developers How easy is it to get an idea of what your product is? @bdougieYO @bdougieYO

50. @bdougieYO @bdougieYO More than just octocats

51. @bdougieYO github.com/dear-github/dear-github

52. What Would Bey Do? @bdougieYO

53. Does this spark joy? @bdougieYO @bdougieYO @bdougieYO

54. @bdougieYO We can’t wait for new letters to solve

55. @bdougieYO

56. GitHub API @bdougieYO sandwich.netlify.com @bdougieYO @bdougieYO

57. @bdougieYO @bdougieYO Developer’s know what they’re doing…

58. @bdougieYO @bdougieYO We can’t assume developers know what they’re doing.

59. Why use the GitHub API? @bdougieYO sandwich.netlify.com @bdougieYO @bdougieYO

60. It sparks joy @bdougieYO @bdougieYO @bdougieYO

61. automate workflows @bdougieYO By leveraging the GitHub API

62. @bdougieYO identify repeated tasks “We {action} every {period of time}.”

63. @bdougieYO @bdougieYO Things needed for API integration 1. Someone older

    and wiser than you

64. @bdougieYO @bdougieYO Things needed for API integration 1. Authentication and

    JWT knowledge 2. Good security practices 3. Webhooks 4. REST endpoints 5. Support forum 6. Domain/Insitutional knowledge 7. Patience 8. Server management
65. None

66. Speed to Success 2. How long does it take to

    go from 0 to using your product? @bdougieYO @bdougieYO

67. Direct @bdougieYO @bdougieYO

68. Netlify @bdougieYO @bdougieYO

69. What is Netlify?

70. What is Netlify? Deploy modern web projects

71. Deploy in seconds?

72. Deploy in seconds? github.com/bdougie/hugo-restaurant-tutorial

73. Deploy in seconds? github.com/bdougie/hugo-restaurant-tutorial

74. None

75. Deployed in seconds (confirmed) @bdougieYO @bdougieYO

76. GitHub API @bdougieYO sandwich.netlify.com @bdougieYO

77. @bdougieYO @bdougieYO How do we solve this reference only problem?

78. @bdougieYO @bdougieYO Things needed for API integration

79. @bdougieYO @bdougieYO Things needed for API integration 1. Authentication and

    JWT knowledge 2. Good security practices 3. Webhooks 4. REST endpoints 5. Support forum 6. Domain/Insitutional knowledge 7. Knowledge of server management 8. Patience

80. @bdougieYO @bdougieYO Things needed for API integration

81. GitHub Apps @bdougieYO @bdougieYO (API + Webhooks + Auth)

82. @bdougieYO @bdougieYO developer.github.com/apps/building-github-apps/creating-a-github-app/

83. GitHub Apps @bdougieYO @bdougieYO Only15 steps and you are done!

84. ( @bdougieYO @bdougieYO Only15 steps and you are done!

85. @bdougieYO @bdougieYO The Craftwork Workshop

86. How fast can I deploy a GitHub App? @bdougieYO

87. GitHub Apps @bdougieYO @bdougieYO Take too long!

88. Channel @bdougieYO @bdougieYO

89. GitHub App in minutes w/Probot @bdougieYO @bdougieYO

90. @bdougieYO @bdougieYO probot.github.com/docs/hello-world/ こんにちは世界

91. GitHub Apps @bdougieYO @bdougieYO Takes too long!

92. You can clone on GitHub in seconds (solved problem, sort

    of) @bdougieYO @bdougieYO

93. @bdougieYO @bdougieYO 1-click Craftwork Workshop

94. @bdougieYO @bdougieYO 1 minute GitHub App

95. @bdougieYO @bdougieYO 1-click Craftwork Workshop

96. GitHub Apps @bdougieYO @bdougieYO In minutes!

97. 1. Faster onboarding will lead to a happy developer 2.

    Identify ways to package up onboarding to embrace channel How long does it take to go from 0 to using your product? @bdougieYO @bdougieYO

98. Reference Materials 3. How easy is it for a developer

    find references and examples? @bdougieYO @bdougieYO

99. Direct @bdougieYO @bdougieYO

100. developer.github.com @bdougieYO @bdougieYO

101. Embedded experience with live data @bdougieYO @bdougieYO

102. @bdougieYO

103. Channel @bdougieYO @bdougieYO

104. @bdougieYO Probot + Octokit

105. @bdougieYO

106. @bdougieYO

107. GraphQL (direct + channel) @bdougieYO @bdougieYO

108. Embedded experience with live data developer.github.com @bdougieYO @bdougieYO

109. @bdougieYO https://ohbarye.hatenablog.jp/entry/2018/05/04/134340

110. 1. Consider SEO, blogs, and community created tutorials 2. Teaching

     is better than direct selling 3. Give developer something to engage How easy is it for a developer find a references and examples? @bdougieYO @bdougieYO

111. 1. How easy to get an idea of what your

     product is? 2. How long does it take to go from 0 to using your product? 3. How easy is it for a developer find a references and examples? Focus on these 3 questions @bdougieYO @bdougieYO

112. Take care of your own mess! @bdougieYO

113. @bdougieYO ❤#) さようなら