Must Have 10+ Years People Experience

Solving a technical problem is relatively easy: there tends to be precedence, easily accessible data, black and white results, and a long list of knowledgeable developers to lean on. People problems are stickier; there are far more variables, no tests you can write, no debugger to use. In this talk, I’ll focus on our biggest issues as developers and community members. We’ll examine what’s broken, what works, and some useful people katas.

More information here: http://ashedryden.com/ruby-midwest-must-have-10-years-people-experience

Transcript

1. must have 10+ years people experience
2. @ashedryden smirk
3. it’s people all the people people people way down
4. programmer good great
5. Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships
6. Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships
7. dream job? maybe not so much.
8. nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope nope DO NOT WANT
9. solve the actual problem
10. what are the problems?
11. I’m part of the problem? what if waaaaaait a minute
12. this is awkward. well.
13. list problem areas
14. 1learn
15. empty your cup
16. beginner's mind
17. learn
18. why? game
19. 1 2 ask questions don’t offer info unless asked
20. 2empathy
21. know that feel, bro
22. we can’t know all the things
23. empathy
24. hacker school rules
25. internalize this stuff
26. no saying “well actually...” 1
27. no feigning surprise 2
28. no backseat driving 3
29. no sexism, racism, or discrimination 4
30. 3listen
31. this slide intentionally left blank
32. ain’t even bovvered, tho
33. listen
34. watch for interruptions
35. 4respect
36. value the time of others
37. come prepared
38. If you aren’t getting or giving value where you are, go somewhere you can
39. :( that’s not cool
40. respect
41. offer to help without expectation
42. 5exception handling
43. my code is totes perfect
44. assume best intentions (yes, this is hard.)
45. graceful degradation
46. bug: will not fix
47. exception handling
48. Apologizing: a recipe
49. 1. Acknowledge. 2. “I’m sorry.” 3. Make amends by learning.
50. 6 ·ate (two.four.six.eight) ·ci ·pre ap
51. who’s made a difference to you?
52. free as in high five
53. appreciate
54. open up twitter yes, right now
55. tell them “thank you” #rubythanks
56. 7model behavior
57. MEETS MINIMUM STANDARDS FOR HUMAN BEING MEETS MINIMUM STANDARDS FOR HUMAN BEING ¡no mas!
58. change is hard really
59. model behavior
60. be the change you want to see in the world
61. be the person you want to work with
62. be the person you want in the issues
63. 8 class You < AwesomeFactory
65. sorry, think I got something in my feels
66. awesome factory
67. do more mentor volunteer organize offer help meet new people get excited teach just do something
68. empty your cup hacker school rules watch for interruptions offer to help apologize like a pro say thank you make more awesome
69. we need to be jerks - encouraging +
70. be excellent to each other ❤
71. thanks! @ashedryden bit.ly/asheRMW