Senior Developer Development
summary
Argues seniority maps to skills not age and cites about 10 years to be senior and an expected senior age near 35, advocates mastering business context (impact mapping, domain‑driven design), user techniques (user research, user story mapping, BDD/specification by example), people skills and deliberate learning using the Dreyfus stages and deliberate practice. Recommends teaching (meetups, blogging, code reviews, Stack Overflow) as practice and gives a concrete team result: €6000 bill canceled after colleagues intervened, showing people skills produce measurable outcomes.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:13YEARS OF EXPERIENCE
- 4:55Years of work experience in the company?
- 13:41STAKEHOLDERS
- 17:02THE GOLDEN RULE
- 22:58Expert
- 23:36DUNNING-KRUGER EFFECT
- 29:15DELIBERATE PRACTICE
- 32:01Public speaking
- 35:22HOW TO START?
related talks
29mRedefining Seniority
18m“47 Years Old: They Still Haven't Noticed …”
38mGet old, go slow, write code!
47mGet old, go slow, write code!
01h 01mSkill-building and Growing in Seniority
38m“Am I Senior Yet?” Grow Your Career
46mSenior Developer with 6 Years' Experience, What Next?
40mBuilding Senior Engineers