Doing nothing at work(seangoedecke.com)
474 points by Sukram21 49 days ago | 159 comments
tl;dr: Engineers should aim for ~80% utilization rather than constantly grinding tickets, because high-impact work (unblocking deals, mitigating incidents, shipping key features) is time-dependent and requires available capacity, attention, and visibility to managers. Staying "loose" lets you notice opportunities, get tagged into important work, and respond calmly under pressure. The author also advises declining glue work, resisting backchannel requests for uncompensated labor, and delaying work on unstable requirements—reserving full-intensity effort for the two or three times a year when stakes are genuinely high.
HN Discussion:
  • ~Incentive structures fail to reward incident prevention, undermining the article's premise in practice
  • Reserving capacity is essential, like mana in RPGs or an athlete's off-season, to handle real demands
  • Quality software engineering inherently requires slack; constant busyness produces worse outcomes
  • ~Glue work is actually formally rewarded at some companies, complicating the advice to decline it
  • Protecting against predatory backchannel requests for uncompensated work resonates strongly