> You should read The Phoenix Project, that will help you understand the rationale. What makes you think I haven't read it? When my company went through its so

> You should read The Phoenix Project, that will help you understand the rationale. What makes you think I haven't read it? When my company went through its so called "devops transformation", first thing our devops advocate did was giving away a dozen or so copies. I understand the rationale. I just happen to not agree with it. In my mind, it's naive to believe that a team would have more than two or three competent coders, with a thorough knowledge of the code base, the high level vision of where that code fits and interacts with the rest of the infrastructure, the skills to quickly fix things, and, on top of that, the willing to be on-call several days a month. And then there is the fact that nobody looks for solutions at 2am, just workarounds.