2 ms·
There are absolutely some industries where this makes sense (life-saving health care, national defense, things like Amazon where you literally stop making money
by pc86 6y ago
There are absolutely some industries where this makes sense (life-saving health care, national defense, things like Amazon where you literally stop making money when things go down).
90% of developers don't work in these industries or on these types of projects. Hell, I work in healthcare, for a private company, and there is zero reason for any of us to be on call. Patient quality doesn't suffer one iota if our software is down, which it rarely is.
It really sounds like you're advocating that developers be on call to "fix" the "problem" that there's no reason for them to be on call?
- potatoz2 6y agoWhat they're saying is that if someone else is oncall, you tend not to deal with the quality issues of the system (it's a negative externality). If the system you own doesn't require any on-call at all, then great. But for those that do (let's say your a web developer for nytimes.com), the code and system owners should be on-call, not a separate ops team. Ideally being on-call is something you barely notice because nothing happens.