If you want developers to have a sense of ownership on their work then yes. The other side of this is knowing how to rollback changes and having your system built to be able to do things quickly, but safely. If your build pipeline takes a long time to get a change out, like a couple hours, this isn't totally feasible.<p>Part of this is building changes with small scope that are easily testable and even for emergency command line changes to have a peer review process with approvals so that issues can be caught early. Being able to dry-run changes in another environment also reduces risk of people.<p>Now I'm not suggesting a junior dev that just started to be given work like deleting a row of bad data out of production in their first week. There should be some common sense around who is getting assigned the work.