Doing nothing at work

▤ Summary

This article argues that software engineers should keep some slack in their schedules instead of staying fully utilized all the time. It says the highest-value engineering work often appears unexpectedly during enterprise deals, incidents, or critical feature launches. It also warns against busywork, excessive glue work, and reacting too quickly to shifting requests that may never ship. The core message is that engineers perform better when they reserve capacity for high-impact opportunities and avoid constant pressure.

▦ Linked Companies