How I Sidestepped ‘Being Glue’
summary
Migration projects run as 95/5 AB rollout experiments using Jupyter notebooks owned by stakeholder teams, with debugging and parity checks stretching one to three months and sometimes a full quarter. A single engineer becomes the default owner, creating a single point of failure, so the response is concrete: define the project lead role, write docs, train colleagues, rotate meeting ownership and quantify glue work in a brag document to preserve technical career momentum.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 4:38Being glue trap
- 8:07Glue work downsides
- 9:10Advice for engineers
- 13:22Breaking free from glue
- 16:12Manager’s role
- 18:38Organizational responsibility
- 19:42Q&A session
related talks
34mThe Survival Guide To Being A Junior Engineer
44mBridging the Gap
19mKeynote Session: The Survival Guide To Being A Junior Engineer
31m"An Intro to Glue Work"
45mClosing Keynote
05mThe Slings and Arrows of Open Source
24mManaging Out: Strategies for Leveling Up
58mKeynote: Seven Habits of a (Mostly) Successful Team