Doing nothing at work(seangoedecke.com)
398 points by Sukram21 4 days ago | 137 comments
tl;dr: Engineers should aim for ~80% utilization rather than constantly grinding tickets, because high-impact work (unblocking deals, mitigating incidents, shipping critical features) is time-dependent and requires available capacity to notice and seize. Staying "loose" makes you visible to managers for important assignments, reduces stress-induced mistakes, and preserves energy for the few times a year when genuine all-out effort pays off. Deliberately avoid glue work, uncompensated backchannel requests, and premature work on unstable requirements—doing nothing is often the optimal move.
HN Discussion:
  • ~Incentive structures fail to reward incident prevention, undermining the article's premise
  • Agrees that being too helpful exposes you to exploitation via uncompensated backchannel work
  • Conserving mental energy/capacity is essential, supported via analogies (mana, athletes, systems at 100%)
  • This echoes established wisdom like Covey's 'sharpen the saw' for knowledge work
  • ~Practical challenges remain: managing perception with overseer-style managers and saying no to friendly clients