Tanya Reilly explains how invisible coordination and support tasks keep software teams successful but can inadvertently stall an engineer's career progression.
Video sponsor: United States Digital Service (usds.gov)
Full talk title: Being glue
Your job title says "software engineer", but you seem to spend most of your time in meetings. You'd like to have time to code, but nobody else is onboarding the junior engineers, updating the roadmap, talking to the users, noticing the things that got dropped, asking questions on design documents, and making sure that everyone's going roughly in the same direction. If you stop doing those things, the team won't be as successful. But now someone's suggesting that you might be happier in a less technical role. If this describes you, congratulations: you're the glue. If it's not, have you thought about who is filling this role on your team?
Every senior person in an organisation should be aware of the less glamorous - and often less-promotable - work that needs to happen to make a team successful. Managed deliberately, glue work demonstrates and builds strong technical leadership skills. Left unconscious, it can be extremely career limiting. It pushes people into less technical roles and even out of the industry.
Let's talk about how to allocate glue work deliberately, frame it usefully and make sure that everyone is choosing a career path they actually want to be on.
About Tanya Reilly
Tanya Reilly is a Principal Software Engineer at Squarespace working on infrastructure and site reliability. Before Squarespace she spent 12 years in Site Reliability Engineering at Google. She is originally from Ireland, but is now an enthusiastic New Yorker. Tanya likes raspberry pi, coding on trains and figuring out how systems will break. She blogs at noidea.dog.
Lead Dev is a community for technical leaders. We have a series of conferences and meetups designed with the needs and pain points of technical team leads in mind. We programme each conference around our three key themes of Team, Tech & Tools. The talks are designed to help very practically with common problems in these areas. To find out more about us, visit:
theleaddeveloper.com/
Why it's here
1 person recommends this
What people say. Recommended as a crucial talk on the career impact of non-technical coordination work in software teams.
s
st1x7on Hacker News • Recommends
On “John Carmack: Career Advice”
> 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: link to this video Summary article: link
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. 0link to this video
Interesting to think of this in the context of Glue Work. link to this video Building culture means handling these opposing forces in a productive manner.