Close and shorten the pain loop as much as possible. If it causes availability pain, it should inflict pain on those who caused it. If the developer wrote terr

Close and shorten the pain loop as much as possible. If it causes availability pain, it should inflict pain on those who caused it. If the developer wrote terrible code, the developer should be paged when the code/stack/framework breaks. If ops/SRE/whatever chose a terrible server platform or cloud provider, they should be paged when the server crashes or goes offline. Two decades of history has shown that the carrot doesn't work in this age of Internet companies. You gotta use the stick. I wished that the carrot works and there are those altruists who have only worked in ideal environments where the carrot works, but they are the extreme outliers. The average lifespan of companies these days is too short for employees to stick around and actually care too much. All jobs these days are gigs, and most are looking for the next one. Why would you waste time fixing your problems in this context? Close the pain loop.