Technical leadership and glue work - Tanya Reilly | #LeadDevNewYork
LeadDev1 HN recommenders · 2020–2022
93K views · talk · evergreen · Uploaded 2019-05-10
Tanya Reilly's LeadDev talk on glue work, the invisible coordination and support tasks engineers do that keep teams successful but can hurt careers.
HN refers to it in career and promotion discussions, including its warning about doing glue work too early in your career.
18:13Try to Rule Fairly and You'll Be Overthrown
CGP Grey
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
32:56Bret Victor The Future of Programming
Joey Reid
19:10Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems"
O'Reilly
54:11Ed Catmull, Pixar: Keep Your Crises Small
Stanford Graduate School of Business
1:18:21"Uncle" Bob Martin - "The Future of Programming"
Paul Stringer's Mobile Tech
58:39Tim Ewald - Clojure: Programming with Hand Tools
ClojureTV
10:48RSA ANIMATE: Drive: The surprising truth about what motivates us
Royal Society of Arts
3 comments from Hacker News
Based on the talk [0] where the OP suggested it number of times. She mentions the engineer being rusty and having significantly fewer code contributions than her peers. In general, if the glue person has intermediate knowledge of the codebase, they'd get promoted without much controversy. In such a case, it should not be difficult for them to bang out a couple of features and ship it, for example. [0] [VIDEO]
> My suggestion is to find gaps that aren't integration efforts, if possible, that are instead extension efforts. Yes! This can go even further and the technical integration work can easily slip into soft/people/team/project/management integration. Here is a talk which warns against doing this kind of glue work too early in your career: Video: [VIDEO] Summary article: [LINK]
Interesting to think of this in the context of Glue Work. [VIDEO] Building culture means handling these opposing forces in a productive manner.