Glue Work Considered Harmful: A Survival Guide for Effective Engineers

This article explores the concept of "glue work" in software engineering. While crucial for team efficiency (e.g., updating documentation, addressing technical debt), this unglamorous work often goes unrewarded, disadvantaging engineers who prioritize it. The author argues that companies don't reward glue work because they want engineers focused on feature delivery, not overall efficiency improvements. The efficient strategy is to apply glue work tactically to projects you're accountable for, ensuring their success, rather than spreading efforts thinly. This isn't cynical office politics; it's based on the reality of low efficiency in large companies and the prioritization of growth over short-term efficiency gains.