Ignites- Title: Management or Technical?
summary
Claim: you can lead and still write code. Cites Puppet experience, grew team from 1 to ~38 and keeps prioritize people over computers. Describes concrete practices: automate your management (document expectations, schedule, and priorities), check your title at the door so technical decisions stay with engineers, avoid putting oneself on the critical path, and mentions building a small chatbot as a recharging technical project that does actually run.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:15Peoria Illinois
- 0:30System Administration
- 0:45Caterpillar Financial
- 1:00Management or Technical
- 1:15People are interchangeable
- 1:30I moved to Portland
- 2:30Growing Teams
- 2:45Management vs Technical
- 3:00Automation
- 3:15Working for me
- 3:30Priorities contexts
- 3:45Ask why
- 4:15Critical Paths
- 4:30Technical Work
- 4:45Career Paths
- 5:00Culture
related talks
51mTeaching and managing for technologists
26mSo you want to be a manager
29mImpact Beyond Code: A Guide to Technical Leadership
10mMicrotalk: Working with Rubyists
01h 01mHabits of a Highly Effective Technical Manager
06mIgnite: Moving from regular sysadmin to DevOps
38mWho is a Lead Engineer today
47mLeading in Tech