Lessons learned after more than 20 years working in IT
summary
Twenty years in IT distills to concrete practices: a first job with 32 new hires and no senior wastes time and money when juniors don’t ask questions, so build mentorship and say no to unsafe requests; run a weekly Friday feedback ritual with breakout rooms and actionable examples (three-person pilots scaled up); turn “laziness” into automation to eliminate repeat alerts; document values and a two-year career action plan to refuse mismatched clients (no gambling work) and protect team mental health because feedback is a gift and automate your laziness.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:55Lessons from junior developer days
- 7:53Challenges as senior developer
- 13:11Becoming a delivery manager
- 18:09Transformation consultant insights
- 25:36Career reflections and advice
- 26:48Q&A session
related talks
40mLessons Learned After More Than 20 Years Working In IT
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
29mBackwards compatible – Lessons from 25 years in software
22mNotes to my younger self
26mAll the things I learnt as a junior developer (so you don't have to)
28mLessons and Expierience from 15 years of Agile Coaching
14mIt's Dangerous To Go Alone Lesson From The Tech Wilderness
58mBackwards Compatible- Lessons from a Quarter Century in Software
