Earlier quoted context omitted.
Well, OK, but this was expected from sysadmins as well. It was always sysadmin who is responsible that the application died, no matter the real reason. Where do you think the idea of putting programmers on call to reduce crashes came from?
> It was always sysadmin who is responsible that the application died, no matter the real reason. Out of the last 15 years of tech experience, I've only seen this be the case in the last 3 years, where the sysadmin/Devops engineer was required to have more ownership beyond "your application is broken, I've restarted it and notified the developer".
Funny. I have seen it for last ten years. And it was not that rare that the sysadmin knew more about system's internals than its programmer.