Tell Us Another Story Grandpa: Lessons Learned over 16 Years as a Developer
summary
Sixteen years condense into concrete lessons: started in ISP phone support, moved into Pearl and corn scripts fixing internal tools, later picks up Ruby and Rails at a university library search company, joins Apposite/Union Metrics, and learns plentiful specifics — employers keep people who provide more value than they cost, managers must protect employees from abuse, remote roles fail when communication lapses, mentorship measurably improves code, and applying engineering (hour‑by‑hour calendar changes) rescues family time.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:38financial asset vs a financial liability
- 6:25protect and insulate employees
- 14:02find a mentor
- 18:50apply engineering principles to personal problems
related talks
39mNew Dev, Old Codebase: A Series of Mentorship Stories
55mAn Elderly Software Developer’s Long Journey through Technology
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
52mNew dev, old codebase: A series of mentorship stories
40mLessons Learned After More Than 20 Years Working In IT
30mLessons Learned: A Developer's Perspective on Teaching & Learning
34mKeynote: Looking Back at a Lifetime of Poor Tech Choices
22m7 lessons learned from becoming a senior engineer