Click any tag below to further narrow down your results
Links
This article lays out seven hard-learned rules every engineer breaks at least once—like “rollback first, debug later,” testing backups by restoring them, and always having a tested rollback plan. It also covers handling external failures, using four-eyes checks for risky changes, logging trade-offs, and avoiding “temporary” fixes that stick around forever.
The author argues that engineers should target around 80% utilization—avoiding nonstop ticket grinding—to keep bandwidth for time-sensitive, high-impact tasks like unblocking deals or incident mitigation. By deliberately doing “nothing” during low-pressure periods and pushing back on non-prioritized work, you stay alert for the right opportunities and reduce stress-driven mistakes.