Back in the day (and still today, sadly) SWEs had nothing to do with how their code was run. You paid Operations Engineers to staff a NOC and build an entire pr

Back in the day (and still today, sadly) SWEs had nothing to do with how their code was run. You paid Operations Engineers to staff a NOC and build an entire practice around preventing and responding to crises. The SWEs would commit their code, push a deploy button, and go home for the day (at 5PM on a Friday), oblivious to any chaos that might ensue. I still meet SWEs who seem to believe they have no responsibility for any failures resulting from their code if it "worked for them in dev". No responsibility to design their code to resist failures or security issues in production, nor re-design it if the current design is failure-prone. No responsibility to performance test, functional test, or check with other teams on what a change might impact at scale. No need to come up with a rollback plan or test it. If their product makes a ton of money, upper management enables this attitude, because nobody wants to kill the golden goose or risk losing its developers. It's a question of priorities. If the business does not require SWEs to care about risk, failure, reliability, etc, then they won't.