Technical leadership and glue work - Tanya Reilly | #LeadDevNewYork

Channel:LeadDev · Length:28:19 · Published:2019-05-10 · Views:93805

Watch on YouTube

Summary

Tanya Reilly's LeadDev talk on glue work, the invisible coordination and support tasks engineers do that keep teams successful but can hurt careers.

Why HN recommends it

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 — HN, 2020

Software practice, open source & careers · Management, leadership & organizations

Subtitles (excerpt)

Hi! So you know the thing where everyone on a software engineering team turns up every day and writes code for 8 hours and then goes home and then later the project is wildly successful? Nobody knows that thing. As Rod just told us, it's a lot more complicated than that. Just finding the clicker. So yeah, coding is important. I don't think that's a very controversial opinion. But there's a ton of other skills that we need to bring to work every day if we want our projects to succeed. Like... Clicker? Clicker? Oh, it's moving. Okay. Like noticing when people are blocked. Noticing when someone on the team is having problems and helping them get unblocked. Reviewing design documents and noticing the thing that's being hand waved. The blur words. What's not gonna work. Or onboarding new people and making them productive more quickly. Or making sure that the team's road map is up to date and not a pile of lies. I call all of this "glue work". It's technical leadership. So we do get some signal for it. You know, the kind of leadership interviews we might do for senior engineers. But sometimes a team ends up with someone who's not senior, like a junior person, who just happens to be good at noticing this stuff. Like, someone...

On Hacker News

> 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] — st1x7, 2020-12
Interesting to think of this in the context of Glue Work. [VIDEO] Building culture means handling these opposing forces in a productive manner. — csours, 2022-02
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… — BossingAround, 2020-11

Related videos