Backwards Compatible- Lessons from a Quarter Century in Software
summary
Over 25 years of practice yields concrete rules: you have about five minutes in interviews to convince someone, be on time and concise, and focus on measurable impact not activity; teams post interview banks on GitHub so publish interview questions matters; keep a living brag doc with PRs and outcomes for reviews; negotiate total compensation not just salary; run weekly one-on-ones and document everything because glue work often goes unrewarded unless the manager explicitly credits it.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:10First Tech Conference
- 2:47My style
- 6:44Getting hired
- 7:33The hiring process
- 11:15Interview questions
- 19:45Dear New Engineer
- 22:34Speak for Your Work
- 30:15Use 101s
- 32:54Hard Truth
- 34:32Work Size
- 36:00Relationships
- 39:20Glue Work
- 43:46Becoming a Manager
- 44:16Things to Remember
- 48:32Peers
- 50:36Documentation
- 52:05Being First
- 56:14Small Companies
related talks
29mBackwards compatible – Lessons from 25 years in software
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
26mAll the things I learnt as a junior developer (so you don't have to)
27mTech hiring is broken' is broken
40mCorporate Success: The Unwritten Curriculum
22mNotes to my younger self
28mLessons learned after more than 20 years working in IT
30mLessons Learned: A Developer's Perspective on Teaching & Learning