> Yes, devs are often enthusiastic because they think they can ditch those boring old operations people who always stop them having fun. I think it's more subt

> Yes, devs are often enthusiastic because they think they can ditch those boring old operations people who always stop them having fun. I think it's more subtle than that. (Also, I think the parent was trolling, but you knew that). It's that there's a certain class of programmers (and/or managers with exclusively programming backgrounds) that truly believe all (technology) problems can be solved with software. If one assumes that belief, then the hostility to someone who believes differently is arguably inevitable. It also explains why, to some, "Devops" is code for "wannabe dev" or some other coding-first role. >Next thing they know they're on call 24/7 and don't get to write application code anymore, just operations stuff... >The truth is the need for ops people doesn't evaporate when you go cloud That explains the dozens of seemingly-identical job postings from tech startups for "Devops" engineers with both experience in the above latest tools and operational experience. Fortunately, they only ask for 1-3 years, which is realistic. > This is the same dynamic that played out with MongoDB. Ultimately, though, did it matter? If we sometimes got fail whales instead of 140 characters, we still didn't get flying cars. Alternatively, for whatever reason (freely flowing VC? low interest rates?), there's too little incentive for low cost or high reliability ops right now.