> It's built for developers who don't like managing servers and working with cron jobs. I had a hard time understanding the target market. Are they referring to frontend developers who are forced to do backend work?
Increasingly, people in one area are expected to take on the responsibilities of other areas. This invariably ends up in disaster the moment you've scaled past the point that inexperienced person can go. Not because that person doesn't have good intentions, or ability to read manuals, but because some things you only learn by doing the hard way.
DevOps tries to turn developers into sysadmins. Sysadmins make fantastic scripts to manage their servers. Developers make fantastic programs. The skills are similar but ultimately very different, the problem domains are very different, and the thought processes required are very different.
"Oh I can just copypasta this from stackoverflow" is a terrible way to develop or administer systems. The danger is squared when it's the area you care less about, as you have even less chance of detecting when you're doing it wrong.
Alas, business needs don't allow for the right thing to be done from the start, which is reasonable as the money needs to go on generating more money and fast.
Which is why every business has technical debt, always and forever, and overpaid consultants will always have jobs pointing out where the problems are for other people to fix.