Hierarchy of Developer Needs -- adapting when things go wrong

Transcript

1. 1.

   Hierarchy of Developer Needs Julia Ferraioli Senior Developer Maslow Advocate

   @juliaferraioli google.com/+JuliaFerraioli
2. 2.

   Financial gain Shiny objects Respect and recognition Utilitarianism Socialization Self

   improvement What drives my community?
3. 3.

   Creative Commons image courtesy of Luc Galoppin

4. 4.

   Image courtesy of my bad planning

5. 5.

   But I’m a developer! I know what my developers need.

6. 6.

   Creative Commons image courtesy of Duncan Hull

7. 7.

   My mistake Reference docs Code samples Tutorials Discussion forum Online

   courses
8. 8.

   This works... sometimes

9. 9.

   Developer Profiles Enthusiasts Founder Enterprise Engineer

10. 10.

    No one hierarchy to rule them all Image used with

    permission of of Mirach Ravaia
11. 11.

    Back to the mistake Reference docs Code samples Tutorials Discussion

    forum Online courses
12. 12.

    Time to shuffle Online courses Tutorials Libraries, SDKs, gems Code

    samples Reference docs
13. 13.

    Time to shuffle Reference docs Paid support Code samples Online

    courses Libraries
14. 14.

    Time to shuffle

15. 15.

    Debugging your hierarchy

16. 16.

    gdb devexp

17. 17.

    Creative Commons image courtesy of Olga Mismatched...expectations

18. 18.

    You have to ask your developers • Hit the pavement

    • Structured engagement • Informal engagement • Research (costly)
19. 19.

    What are the obstacles? • Cognitive disconnect • Lack of

    direction • Absence of trust • Problematic community Creative Commons image courtesy of Grant Montgomery
20. 20.

    Creative Commons image courtesy of Thomson Safaris Plan of Attack

21. 21.

    Creative Commons image courtesy of Arne Hendriks

22. 22.

    Thanks! Images by Connie Zhou @juliaferraioli google.com/+JuliaFerraioli

23. 23.

    Creative Commons image courtesy of David Ashleydale