After years of excellence as a developer who gets things done, you are rewarded with a leadership title and more responsibility. Only now you are expected to manage people and not just code. What motivated you to improve doesn't seem to always work on your team. So what do you do? We will explore the art of managing talented people and learning what the human needs for guidance and support from their leader.

1. The Care and Feeding of Software Engineers
Heather Downing
@quorralyne

8. –Bill Gates
“Success is a lousy teacher.
It seduces smart people into thinking they can’t lose.”

10. –John C Maxwell
“People buy into the leader before they buy into the vision.”

11. Leadership is a
MUSCLE

12. What Developers Want from Leaders
Good leaders that make them feel safe
(safe to fail, to confide in, believes in you)

13. What Developers Want from Leaders
Have vision and higher purpose for their work
(provide education, opportunity, growth beyond ourselves)

14. What Developers Want from Leaders
Flexible and empathic during personal challenges
(No hard and fast rules, people before profits)

15. A Technical Leader will…
Listen
Respect
Encourage
Recognize
Empower

16. LISTEN

17. RESPECT

18. ENCOURAGE

19. RECOGNIZE

20. EMPOWER

21. The Care of:
JUNIOR DEVELOPERS

24. The Care of:
MID-LEVEL DEVELOPERS

27. The Care of:
SENIOR DEVELOPERS

30. The Feeding of:
THE INTROVERT

31. The Feeding of:
THE EXTROVERT

32. The Feeding of:
THE OPTIMIST

33. The Feeding of:
THE PESSIMIST

34. The Feeding of:
THE SENSITIVE

35. The Feeding of:
THE BOLD

36. The Feeding of:
THE BRIGHT

37. The Feeding of:
THE DOWNHEARTED

38. The Feeding of:
THE DISCONNECTED

39. How to treat your
team as a whole

40. Development Lead Tips
Allow developers to do their jobs
Handle non-development work needs
Be moderately responsive and reachable
Make regular one-on-ones a priority
Emphasize quality code over quantity or velocity
Avoid task switching (multiple projects, two many interruptive meetings)
Be the shield for your team when challenges arise

41. Takeaways
Give away control and create opportunities for others to grow
Drive for autonomy, mastery, and purpose
Allow your team to fail - through failure we learn
Teach others and emphasize you are learning as well
It’s OK to not know everything

42. –Stephen Haunts
“Trust your teams judgement. You may need to step
into make decisions and priority calls, but this will be
on the information provided by your team. If you get
this right, you should have a good autonomous and
self directed team.”

47. Be a gate opener
Not a gatekeeper

48. STAY CURIOUS.SLIDESHARE.NET/QUORRALYNE | GITHUB.COM/QUORRALYNE
Heather Downing
@quorralyne | quorralyne@gmail.com | www.quorralyne.com