How to Lose an iOS Developer in 10 days
summary
Lists concrete practices and outcomes: monthly 15‑minute walks and quarterly 30‑minute reviews for feedback, a weekly show‑and‑tell on Wednesdays at lunch, an open conference budget and project‑selection veto by the whole team, hiring by team thumbs‑up. Claims include growth via intentional learning and junior–senior pairing, transparency to avoid silos, and a hard result — lost half the iOS team in the acquisition — used to argue which changes actually retain developers.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:15Hello, My Name is Josh.
- 11:20Growth
- 14:30"How do I become a 'Mid-level' Developer?" "Should I become a Manager?" • Think about Teaching Hospitals.
- 15:56Feedback
- 18:33Trust
- 19:52Challenging Work
- 22:11Culture
- 24:22The Rest of the Team
- 25:32Transparency
- 28:53The Future
related talks
30miOS at
43mFun with iOS Enterprise Apps
50mThe Effective Developer - Work Smarter, Not Harder
21mManipulating organizational dynamics to improve app development processes
01h 03mThe Effective Developer - Work Smarter, Not Harder.
30mHow Falling Behind Actually Got Me Ahead
30mDeveloper First – A New Leadership Mindset
32mMess around and find out