Are you sure? Amazon is getting flak for that lately (in e.g. Yegge's rant), from having all of its developers on-call. You should be around to fix something you push if it breaks things, but that's not the same as being on-call at all hours for any given coworker's or manager's standard of "going hatstand".

>You should be around to fix something you push if it breaks things

Which has another advantage over Amazon's pager policy: if you are up at 3am, only semiconscious, you are likely to be more useful fixing code that you broke (because you just touched in the last day or two) than some other coworker's mistake.

Agree, with the caveat that those who carry the 3am possibility are allowed to delegate at their own risk.

i.e. the real rule is "nothing happens to prod without the agreement of those at the sharp end".

That allows good devops fun to happen with fewer ops bottlenecks, if some devs can provide enough ops-chops to keep the real ops people happy.

[Also note in passing that such devs are likely to be in the "second wave" of 3am people if things go sufficiently pearish.]

Agreed - that is a general rule too. E.g. those that do the actual work make the final call on which technology, language, database, whatever to use - not some "architect".

I love this explanation. Note my username :)