Leading in Tech
summary
Argues leadership is for the people being led not the leader, and lays out concrete roles: mentor, tech lead, principal/staff, public leader, manager and senior leadership, with practical actions — run regular one‑to‑ones, build career progression frameworks, mentor formally, publish blog posts, speak at meetups, work on OSS (mentions symphony core and version 5.1.2) and contribute to projects at bud (services primarily written in Go). Recommends the book "The Manager’s Path" and illustrates stress handling with the poop umbrella/funnel/fan metaphor, emphasizes listening, generate clarity and speak last.
AI-written summary · about
chapters (27)
- 0:00Intro
- 1:48LEADERSHIP IN TECH
- 3:01WHAT IS LEADERSHIP?
- 4:30WHAT'S THE POINT OF IT?
- 5:32SO WHO IS A LEADER?
- 5:44THE DIFFERENT FORMS PHP UK 1 OF TECH LEADERSHIP
- 5:55MENTOR
- 9:54PRINCIPAL / STAFF
- 11:56BEING A LEADER IN
- 14:42MANAGEMENT
- 17:42SENIOR LEADERSHIP
- 19:39PRINCIPLES
- 20:02LISTEN
- 22:30GENERATE CLARITY
- 23:58BE AWARE OF POWER
- 27:58SPEAK LAST
- 29:07YOU'RE ALL
- 30:12KEEPING OR BEING
- 31:29MANAGE PHP UK STRESSES
- 32:57FIND GOOD LEADERS
- 34:21PEOPLE YOU CAN
- 35:02SOMEONE WHO WILL
- 35:29A VISION AND A VIEW
- 36:04PEOPLE WHO WILL PHP UK RESPECT YOU BACK
- 36:30SOMEONE WHO WANTS TO HELP YOU GROW (NOT JUST THEM)
- 37:22BECOMING A
- 39:35BOOKS
related talks
47mLeading in Tech
35mTalking With Tech Leads
45mBecoming a Leader in Tech: How to boost your career without losing your mind
16mThe secret to technical leadership
29mThe Constant Life of a Tech Lead
47m"Talking with Tech Leads"
58mMy Journey to Understanding Technical Leadership
49mPractical Leadership for Software Developers
