The Influential Software Engineer
summary
Argues that people and culture, not tech, break projects and offers concrete practices: start with one test a day to chip away at legacy, post code coverage numbers to raise coverage (example moved from single digits to mid‑50s), run a project room pilot to prove workspace changes, fix compiler warnings (800 warnings ignored is a problem), and use an influential ally to introduce tools (GitHub pilot becomes enterprise licenses). Claims $2M can unlock $20M in value with the right story.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 1:48Software is a people project
- 3:54Why influence matters
- 5:39Culture shapes everything
- 8:45Culture kills good ideas
- 11:36Changing culture takes time
- 13:00Tools don’t fix culture
- 15:47Innovation beyond tech
- 17:29Start fresh when possible
- 18:31Working with legacy code
- 19:32The arsonist firefighter
- 21:15High expectations matter
- 22:39Code smells and bad habits
- 25:07Tests aren’t enough
- 27:54Metrics with purpose
- 28:57Leverage your tooling
- 30:01Cultural shifts are hard
- 31:45Make change their idea
- 33:29Values and team norms
- 34:32Simplicity over complexity
- 36:14Essential vs accidental complexity
- 37:58All code becomes legacy
- 38:40Focus on the human
- 40:46Document everything
- 43:57Most problems are misconceptions
- 45:41Share knowledge actively
- 47:29Golden rule for engineers
- 48:33How to get buy-in
- 50:17Hammer vs ninja approach
- 53:47Find influential allies
- 57:21Use indirection wisely
- 58:03Know your reputation
- 59:07Be helpful and respectful
- 1:00:11Q&A
related talks
31mThe Effective Developer - Work Smarter, Not Harder
48mThe Effective Software Architect - Work Smarter, not Harder
17mGood to Great
50mThe Effective Developer - Work Smarter, Not Harder
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
01h 03mThe Effective Developer - Work Smarter, Not Harder.
20mFailing Can Be Good! Bringing a Growth Mindset to Every Project
58mHow to survive and thrive as an engineering leader
