> I largely believe developers should be responsible for their work
Definitely
> which includes meeting the support requirements out of hours
Definitely not
Definitely
> which includes meeting the support requirements out of hours
Definitely not
I'm not good with dealing with issues with a deployed product while I should be busy living my life.
Instead, you think some ops guy should do it?
End of the day, an Ops guy who is not part of the development team can't really do all that much when a bad commit brings down the system. Sure, we can take a stab in the dark and roll-back, but we don't know if that's going to make the problem worse, or we can restart it but that's about the easiest thing in the world to automate.
So, why not get the experts of the system, who rolled out the change, and undertook the quality control, to be part of the team that fixes the outage (irregadless of what time we do it at)? Who is better suited?
How does an on-call rotation prevent this?
Where does the responsibility end? At me doing the best job possible under the circumstances, all that could be expected of a human being.