1 / 30

Riding the Paradox as a Lead Developer

When you were just a developer, things seemed so simple. Sometimes it was a choice between using several libraries, or working out the right algorithm to solve a problem. Making decisions seemed really easy. When you are playing the Lead Developer role, decisions no longer seem black and white and you have several competing priorities.<br><br>We will explore the common paradoxes a Lead Developer experiences such as keeping technically relevant and developing better people skills, focusing on delivery software and supporting learning and encouraging improvements and maintaining consistency. Come away from this talk recognising the paradoxes other Lead Developers share with you and how to successfully solve them.

thekua
Télécharger la présentation

Riding the Paradox as a Lead Developer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. @patkua RIDING THE PARADOX AS A LEAD DEVELOPER

  2. ABOUT @PATKUA Architect Developer Leader Coach Life-long learner Author http://tiny.cc/twtl http://tiny.cc/retros 2

  3. 3

  4. Developer 4

  5. Manager 5

  6. Lead Developer 6

  7. 7

  8. PARADOXES The blue button is true The red button is false 8

  9. PARADOXES 9

  10. VS Staying technical Enabling people 10

  11. VS Going faster Learning 11

  12. VS Delivering Innovating 12

  13. VS Consistency Improvement 13

  14. VS Being Transparent Protecting the Team 14

  15. VS Business Needs Techncial Needs 15

  16. RIDING THE PARADOX 16

  17. RIDING THE PARADOX 17

  18. 1. 18

  19. Lead Developer 19

  20. You are not alone… Lead Developer 20

  21. You are not alone… Lead Developer 21

  22. You are not alone… Lead Developer 22

  23. 2. 23

  24. Be comfortable with uncertainty Find your feedback loops 24

  25. 3. 25

  26. Don’t take a binary approach 26

  27. AND not OR 27

  28. Lead Developer 28

  29. 1. You are not alone 2. Find feedback cycles Don’t take a binary approach 3. AND not OR 29

  30. THANK YOU For questions: PATRICK KUA @patkua

More Related