Taking Lead
summary
Personal leadership emerges as concrete practices not grand phrases: running a small business for 13 years, founding Boulder Ruby and rescuing legacy projects produce repeatable lessons. Claims include leadership as a social influence that maximizes others’ efforts, and a technical lead must supply knowledge, make technical decisions, own communication and mentoring. Prescribed tools: Kaizen (plan do check act) for continuous improvement, a feedback rubric—Actionable, Concrete, Kind—and Radical Candor—care personally, challenge directly—proven useful in team turnarounds.
AI-written summary · about
chapters (21)
- 0:00Start
- 8:24Leading in software
- 10:40Senior vs Mid
- 12:43Know the purpose
- 13:59Know yourself
- 15:34Know your team
- 16:13Stay current
- 18:01Actions matter
- 18:37Act with integrity
- 19:07Deliver quality
- 19:59Kaizen -philosophy
- 20:33Kaizen - action
- 23:37Be autonomous
- 25:11Look to help
- 25:51Mentoring
- 26:51Communication
- 29:12Feedback is a gift
- 30:03Giving feedback
- 31:35Receiving feedback
- 34:34Radical candor by Kim Scott
- 35:39It's not easy
