3 ms·
From a developer perspective, DevOps is when you fire all the competent operations people, and then force developers (that chose not to be in ops) to operate th
by hedora 4y ago
From a developer perspective, DevOps is when you fire all the competent operations people, and then force developers (that chose not to be in ops) to operate the code they wrote.
This burns out developers (bait and switch tends to do that), and with silicon valley's standard 4 year vesting cliff, the people that wrote the software just quit and go elsewhere (or get promoted out of the team) about a year after whatever system they built hits prod.
Now (since hiring competent ops people isn't shifting left or right or whatever), you need to hire more systems developers, and pay them hazard pay to operate other people's abandoned garbage. (It is garbage because the previously burnt out group of systems engineers was constantly distracted by things they do not care about. They were constantly distracted with prod issues because they are bad at ops.)
I've worked in devops teams, and with competent operations teams. The latter ends up creating a much higher quality of life for the developers and ops team and also a better product.
In related news, hiring an optometrist to clean your teeth is a bad idea, even though they went to med school.