Just Be Fucking Awesome

As presented at Refresh Denver on 3/12/2014

1. Why Developers Quit Jeff Casimir / @j3 / Turing.io
2. Great Teams are Built Jeff Casimir / @j3 / Turing.io
3. Developing Mastery Jeff Casimir / @j3 / Turing.io
9. Just Be
   Fucking Awesome Jeff Casimir / @j3 / Turing.io
11. Take a Moment
13. The Long Game
14. Most valuable asset?
15. Is it thename?
16. Is it theproduct?
17. Is it thecustomers?
18. Delete them all.
19. It’s the people.
21. Why be a one hit wonder?
23. Developer Happiness
24. Why do you have a
    beer fridge?
25. Why churn out t-shirts?
26. Abraham Maslow
27. Physiological
28. Physiological Safety
29. Physiological Safety Belonging
30. Physiological Safety Belonging Esteem
31. Physiological Safety Belonging Esteem Self Actualization
32. Food, Beer, Couches Physiological
33. Food, Beer, Couches Great Paychecks Safety
34. Food, Beer, Couches Great Paychecks T-Shirts Belonging
35. ? Food, Beer, Couches Great Paychecks T-Shirts ? Esteem Actualization
37. Building Esteem
38. Esteem is built backwards.
39. How do you reflect?
40. Continual improvement does not mean only focusing on the problems.
41. Esteem dies
42. Esteem dies fromfocusing on blame.

43. Esteem dies fromweak management.

44. Esteem dies from assholes.
45. Esteem thrives
46. Esteem thrives in communities.

47. Esteem thrives in celebration.

48. Esteem comes from shipping.
49. Make sure there aren’t bugs/issues before going to production. code reviews Explore the story of code.
50. Developers do what they’re good at. cross-pollination Collaboration is promiscuous.
51. Figure out what went wrong so it doesn’t happen again. retrospectives Amplify what went right.
53. Self-Actualization
54. Who do you want to be
    when you grow up?
55. Dreams versus goals
56. You need a trajectory.
58. Becoming a Developer
59. “DO IT BY MY OWN!”
60. I loved video games.
61. I really loved hardware.
62. I knew hardware
    was made by nerds like me.
63. If they could do it,
    I could do it.
64. Step one of becoming
    the person I wanted to be.
65. • Ignition • Deep Practice • Master Coaching
67. Ignition
69. What’s possible
70. Someone you can
    identify with
71. Someone you can
    aspire to become
72. This is why
    diverse voices matter.
75. Ignition is about belief
76. Imitate then innovate
78. Deep Practice
80. “Five Years Experience”
81. Deep practice is not busy.
82. Deep practice is not hard.
83. Deep practice is difficult.
84. Deep practice pushes limits.
85. You tell your friends about it.
86. Deep practice builds
    scar tissue.
87. Your day-to-day is
    not difficult.
88. • Algorithms • Data Structures • User Experience • Performance Optimization • Code Under Constraint
89. • Code Katas • Refactoring • Open Source • New Languages • Teaching / Mentoring
90. Deep practice needs
    constant feedback.
92. Getting Feedback
93. The computer gives
    unrelenting feedback.
95. Your career is built on
    luck & error messages.
96. That’s not predictable.
97. That’s not sustainable.
98. That’s not enough.
99. Sustained growth necessitates
    master coaching.
100. exercism.io
101. dribbble.com dribbble
103. Master Coaching I:
     Feedback
104. 75% Instructive
105. Feedback is purposeful.
106. Your variables are poorly named. specific Your variables should be snake_cased.
107. The ad needs more “pop”. measurable The ad needs to be readable at 1000 feet when printed 12’x12’.
108. This class mixes multiple concerns. actionable Responsibilities need to be 
 extracted into child classes.
109. Your Backbone app is slow. 
 Rewrite it with Angular. realistic Your app is slow. 
 Add monitoring to find out why.
110. The app you wrote last year is bogging down in production. timely Your latest feature is 
 slowing down in CI.
111. • Specific • Measurable • Actionable • Realistic • Timely
113. Master Coaching II:
     Guidance
114. What ideals do you strive for?
115. Ideals can never be
     fully achieved.
116. I keep all lines of code shorter than 80 characters. ideals Code is read more than written, 
 so I value readability over cleverness.
117. Exemplars help
     measure progress.
118. Code should be well written. exemplars Well written code stays under 
 80 columns per line.
119. Ideals set your direction,
     Exemplars show growth.
120. Coaches help turn ideals
 into action plans.
121. You want to become
122. • JavaScript • Evented Programming • Documentation • Taking Criticism • Extreme Running
124. A coach helps define ideals, and a pathway of exemplars.
125. Feedback corrects course.
126. Growth plans change,
     the goal remains.
128. Master Coach
129. You need a dedicated coach.
130. You need a
131. A person whose
     only responsibility
     is making you better.
132. • Empathy • Expertise • Experience • Organization • Passion
133. Great coaching 
 builds dynasties.
134. This is your whole life.
136. Just Be
     Fucking Awesome Jeff Casimir / @j3 / Jumpstart Lab Ignition Practice Coaching
137. And one more thing...
141. “The best junior developer
     I’ve ever interviewed.”
142. turing.io
143. Just Be
     Fucking Awesome Jeff Casimir / @j3 / Turing.io Ignition Practice Coaching