How to Motivate Your Developers
summary
Argues that concrete fixes win: a Quebec study finds salary ranks first, so resolve pay early; give adapted tools like profilers and paid licenses to remove blockers; onboard beginners with prioritized task lists, check two or three times a day, and validate deliverables quickly; grant experts trust and autonomy for experts over technical choices and time. Avoid last‑minute requirement changes and arbitrary deadlines, add schedule buffers, fund conferences and one‑day retreats (three‑week ski claim yields two months’ productivity in two weeks).
AI-written summary · about
chapters (29)
- 0:00Intro
- 1:21Anna Filina
- 2:48How management sees developers
- 5:29The importance of salary
- 6:56Adapt the tools
- 13:19Dont judge
- 15:29Ask questions
- 16:36List tasks
- 24:17State of emergency
- 26:06What drives people
- 27:15Definition
- 28:32Motivation
- 33:06Identifying Goals
- 35:27Things to Avoid
- 36:59Social Events
- 38:34Fun Committee
- 39:17Chairs
- 40:15Chair example
- 40:33Fun stuff
- 42:22What I do
- 43:05Hackathons
- 43:22Open space vs cubicles
- 45:11Facetime
- 46:32Difference between paid and unpaid volunteers
- 47:59Productivity phases
- 50:02Disruptive cycles
- 51:49Critical path
- 55:50Are others less motivated
- 58:14Are others going the extra mile
related talks
34mBuilding a Culture For Developer Productivity
27mTechnical Excellence: Why does it not stick even now?
33mMeasuring Developer Productivity: the good, the bad and the data
44mDeveloper Joy – How great teams get s%*t done
49mPractical Leadership for Software Developers
33mThe Care and Feeding of Software Engineers
51mEffecting Change—The Art of Leading Teams
33mHow to Enhance the Skills of Experienced Developers