Summarizer

Glue Work Recognition

← Back to Lessons from 14 years at Google

While glue work like technical cleanup and process improvement is vital for a healthy codebase, it is often treated as invisible or even a nuisance by management and peers who prioritize feature output over maintenance. Commenters highlight a frustrating lack of internal recognition for these efforts, noting that significant technical improvements can sometimes be met with hostility from colleagues who view the work as an unnecessary risk. The consensus suggests that the primary challenge is not just managing these tasks, but rather convincing leadership that "invisible" contributions are as valuable as non-glue work. Without this institutional buy-in, engineers are left with the difficult choice of performing unrewarded labor or letting systems fail to demonstrate the necessity of their efforts.

3 comments tagged with this topic

View on HN · Topics
Rightly said. I spent good amount of time cleaning up 15 year old codebase and removed almost 10MB of source code files which was being part of production build and it was never used. This helped reduce the build time. I thought I'd get appreciated from everyone in the team, but it was never acknowledged. In fact my PM was warried and raised an alarm for regression. Even though I was 100% confident that there would not be any regression, the QA and PM got annoyed that I touched a working software and they had to do extra work. I then posted on LinkedIn about this achievement to get my share of appreciation. :)
View on HN · Topics
> 13. The work that makes other work possible is priceless - and invisible. > Glue work - documentation, onboarding, cross-team coordination, process improvement - is vital. ... The trap is doing it as “helpfulness” rather than treating it as deliberate, bounded, visible impact. Timebox it. Rotate it. Turn it into artifacts ... make it legible as impact, not as personality trait. I see my own experience in this, but I don't think he's identified the problem correctly. Timeboxing, rotating, etc, is easy. Convincing management that it is as important as non-glue work and therefore worth allocating your time for it is the hard part. And if you can't do that, you end up stuck in the situation described. The other option is to just let things fail of course, but then you have to convince both management AND the rest of your team to do this, otherwise someone else will just pick it up between the cracks too.
View on HN · Topics
#12 is so simple yet so true. Great list thanks for sharing.