> When you push software and hardware beyond its limits, that means lots of emergencies, lots of firefighting. It's really not rare to have to argue for having

> When you push software and hardware beyond its limits, that means lots of emergencies, lots of firefighting. It's really not rare to have to argue for having any kind of redundancy in hardware or software ("we can't justify the expense of a warm spare, or even a cold spare", "But this is the mission critical software our entire business relies on. Every second it's down is tens of thousands of dollars down the drain", "yeah, but we just don't have the budget for it, we need that for the CEO's golf trips".) > This is the continual story of sysadmin life. .... It's just sheer constant stress courtesy of management that just don't give a shit while things are working, and then lay a crap load of blame on you when things fail. yes, this, a thousand times; my job security lies in my shit eating grin and capacity to ignore exactly this structural idiocy.