8 Things to Consider When Skilling Up Your Dev Team
summary
Claims eight concrete considerations for upskilling and gives a toolkit of practices rather than abstract advice: version control, CI/CD pipelines, smoke tests and parameterize build scripts as immediate fixes, plus measuring backlog causes and dedicating 30–40% time for tech debt as a policy. Notes a hiring reality — waiting half a year for a front‑end dev — and reports building workshops and a simulation game that enumerates practices (75 practices became ~150) to train teams; the workshops and game run and expose where improvements succeed or blow up.
AI-written summary · about
chapters (10)
- 0:00Scaling dev team skills
- 3:18Risks of understaffed teams
- 6:11Defining dev team roles
- 9:04Quality through dev practices
- 14:21Workshop concept
- 18:39Upskilling approaches
- 24:39Innovation and technical debt
- 29:17Team learning strategies
- 33:09Eight upskilling considerations
- 34:53Q&A
related talks
57mHard truths and soft skills: 10 pieces of advice for novice game devs
33mHow to Enhance the Skills of Experienced Developers
33mPower-Up Your Team: Soft Skills That Level Up Game Dev Collaboration
28mBuilding happier engineering teams
30mEquipping your team to support junior developers
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
33mWhat it takes to become a great developer!
01h 04mHow to Motivate Your Developers