Technical leadership and glue work - Tanya Reilly | #LeadDevNewYork on HackerTube: recommended by 1 Hacker News commenter across 1 month, 2020–2022.
talk · intermediate · evergreen
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.
“Here is a talk which warns against doing this kind of glue work too early in your career”
3 Hacker News comments link this video. Each one links back to its thread.
> 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: ▶ this video Summary article: [link]
in “John Carmack: Career Advice” · View on HN
Interesting to think of this in the context of Glue Work. ▶ this video Building culture means handling these opposing forces in a productive manner.
in “You have two jobs (2017)” · View on HN
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] ▶ this video
in “Being Glue” · View on HN