> The articles I read are actually about AWS killing ops in favour of more devops, because apparently AWS makes ops so easy your devs can do it during their lun

> The articles I read are actually about AWS killing ops in favour of more devops, because apparently AWS makes ops so easy your devs can do it during their lunch breaks. Nonsense is an understatement... We, as technologists spent YEARS getting ourselves into some sort of sane silo's because the tools in each area were becoming more complex. Operations, Database, Backend, Front end, and arguably now mobile as different roles. In many places that meant building walls and silo's that were hard to bypass (for good reason) but it made getting problems fixed exceedingly difficult, especially where the rubber met the road (code running on servers). The desire to have open communications isn't the desire to eliminate jobs or roles, but a desire to make actually solving the problems of running an application, doing good engineering easier. This was the intent of Dev-ops collaboration, and doing it out in the open as partners! The problem is that business have taken this and run with it as a reason to curtail resources. Lets take another example that hacker news likes to talk about, Agile. I can't tell you how many agile coaches advocate for everyone on an engineering team being able to accomplish ever role. Not only is this naive but is potentially a source for pain further down the road. I had to think about why Agile coaches were advocating this, and the conclusion that I came to was that "business" likes it. Dev-Ops is now code for "full stack", now code for "we expect you to do everything"... It doesn't scale and further down the road creates far more problems than it solves.