I'm on-call all the time, and the first thing I've taught myself is to not glorify it like some superhero saves the day worship. I'm both proud and (slightly) a

I'm on-call all the time, and the first thing I've taught myself is to not glorify it like some superhero saves the day worship. I'm both proud and (slightly) ashamed each time I handle an incident. It's not a virtue. How many people who were writing blogs or creating open source tools before signed an on-call oath or declaration? Does that mean they're all wrong or unqualified? On call avoidance should be rewarded more than on call superheroism. People managing software fail to realize it. Avoidance is stashing enough operational bullet points, mental checklists and manpages. Everything is generic — because your use case and your operating environment is ONLY yours. Postgres has hundreds of parameters. Nothing is specific or made to satisfy you. If it doesn't, then you don't call the parameter as generic. You choose what to apply for your environment and expectation. What you're saying is both a wrong reward cycle and it was also not necessary or practical before AI.