Lessons Learned After More Than 20 Years Working In IT
summary
More than 20 years in IT trace a path from junior developer learning Pascal 7 in Spain to principal consultant at Contino/Cognizant, with roles as senior dev, team lead, delivery manager and transformation consultant. One early job hires 32 juniors, zero seniors, forcing a rule: ask questions or waste days on wrong work. Teams adopt a simple ritual of feedback straight away and weekly reviews, which measurably tightens collaboration. An ops engineer’s automation from laziness leaves scripts still used years later; work for a pharma client targets and reduces production cost of medicines.
AI-written summary · about
chapters (14)
- 0:00Introduction and nerves
- 1:59Communication in IT problems
- 3:51Career roles and self-doubt
- 6:25Junior developer struggles
- 10:18Becoming a senior developer
- 13:11Feedback and growth
- 17:30Delivery manager insights
- 20:22Laziness as automation engine
- 22:11Transformation consultant focus
- 25:24Imposter syndrome and career goals
- 32:53Asking questions and assumptions
- 34:20Automation and learning
- 35:46Sharing vulnerabilities and growth
- 38:14Career decisions and empowerment
related talks
28mLessons learned after more than 20 years working in IT
47mPersonal Retrospective After 15 Years in the Software Testing Industry
27mTell Us Another Story Grandpa: Lessons Learned over 16 Years as a Developer
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
34m7 tips for Senior Engineers
35m10 Lessons for Growing Junior Developers
30mLessons Learned: A Developer's Perspective on Teaching & Learning
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career