Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to Lose an iOS Developer in 10 Days

Josh Johnson
August 19, 2015

How to Lose an iOS Developer in 10 Days

From 360|iDev 2015 in Denver.

Are you leading a team of iOS developers? How do you find them? What about your team makes them want to be there? What makes them stay there?

Are you an iOS developer looking for a great place to work? What do you look for? What makes you decide to stay there?

This talk will cover all these questions by talking about things you shouldn’t do. How do you make an environment that drives iOS Developers away? What are the traits that lead to horrible workplaces? In talking about building a horrible environment for iOS developers, this session show what actually makes a great environment.

Josh Johnson

August 19, 2015
Tweet

More Decks by Josh Johnson

Other Decks in Business

Transcript

  1. View Slide

  2. Hello, My Name is Josh.

    View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. Acquired by
    Ticketmaster
    (on April 1st)

    View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. View Slide

  13. Meet Dave

    View Slide

  14. He works over
    at Evil Corp
    (Dave has told me a lot of
    stories)

    View Slide

  15. “Hi Dave, it's 8:10am and
    we noticed that you
    weren't at your desk. You
    must be there by 8:00am.”
    — Evil Corp's HR Manager on Dave's first day.

    View Slide

  16. “Photoshop is too
    expensive, here's a
    pirated version from a few
    years ago.”
    — Dave's Manager

    View Slide

  17. “No you can't go to this
    365 iDeveloper thing, you
    already know how to do
    this and there is no
    budget”
    — Dave's Manager

    View Slide

  18. “I don't really understand
    Objective-C so rewrite
    that stuff in C# using my
    libraries."
    — Dave's Manager

    View Slide

  19. “It's okay if you work from
    home, but I need you to
    report everything you do
    and the times so I can be
    sure you were working”
    — Dave's Manager

    View Slide

  20. “How many developers
    do we need? Can you just
    do Android too?”
    — Dave's Manager

    View Slide

  21. “Stop bitching and just do
    your work!”
    — Dave's Manager

    View Slide

  22. View Slide

  23. Dave just
    resigned.

    View Slide

  24. What was great at
    Two Toasters?

    View Slide

  25. Growth

    View Slide

  26. Growth
    • Intentional Learning
    • CocoaBrains
    • Swift Study Group
    • Conferences (360|iDev, WWDC)
    • Community (CocoaHeads, NSCoder Night)
    • Apple Announcements

    View Slide

  27. Growth
    • “What happens after I'm a Senior Developer?”
    • “How do I become a 'Mid-level' Developer?”
    • “Should I become a Manager?”
    • Think about Teaching Hospitals.

    View Slide

  28. Feedback

    View Slide

  29. Feedback
    • Monthly 1:1
    • 15 minute walk
    • “How are you?”
    • Quarterly 1:1
    • 30 minute talk
    • Review and make new Goals

    View Slide

  30. Trust

    View Slide

  31. Trust
    • If you don't trust your team then why are they there?
    • Avoid the “Hands of the VP” Syndrome

    View Slide

  32. Trust
    • If you don't trust your team then why are they there?
    • Avoid the “Hands of the VP” Syndrome
    • Micro-managers, please leave.

    View Slide

  33. Challenging Work

    View Slide

  34. Challenging Work
    • It might not be a good fit. That's OK.
    • During 1:1, ask “Are you bored?”.
    • The team can be involved in what projects to even take on.

    View Slide

  35. Culture

    View Slide

  36. Culture
    • Maintaining a mindset of improvement and optimization.
    • Respect each other, respect clients, respect time.

    View Slide

  37. The Rest of the Team

    View Slide

  38. The Rest of the Team
    • People want to work with people who will challenge them.
    • The team is included in deciding who they work with.
    • Take the time to hire right.

    View Slide

  39. Transparency

    View Slide

  40. Transparency
    • Show and Tell
    • Actively share what other teams or the leadership team is
    doing

    View Slide

  41. View Slide

  42. “Um, Josh, these are all
    really obvious”
    — You, right now.

    View Slide

  43. View Slide

  44. The Future

    View Slide

  45. Thanks!
    Josh Johnson
    @jnjosh

    View Slide