2 ms·
First. DevOps is a culture not a job most places have so many DevOps roles because they are doing it wrong. In the olden days of 10 years ago, most operations
by jeffwask 4y ago
First. DevOps is a culture not a job most places have so many DevOps roles because they are doing it wrong.
In the olden days of 10 years ago, most operations teams worked around the clock to service the application. Like every day there would be someone on my team doing something after hours usually multiple. Tools like Kubernettes, Cloud (AWS, GCP, Azure) have added significant complexity but moved operations to more of a 9 to 5 gig. Less and less do I see after hours deployments, weekend migrations, etc. Even alert fatigue goes way down because things are self healing. This is on top of being able to move faster and safer, scale instantly, and everything else.
Operations side used to be a lot of generalists admin types and DBA's. With today's environment, you need a lot more experts. AWS alone has 1 trillion services and 2.4 billion of those are just different ways to deploy containers. So you see a lot more back end roles because it's no longer automate spinning up a couple servers, install some software, deploy, monitor and update. It's a myriad of complex services working together in an ephemeral environment that no one person understands anymore.
- fertrevino 4y agoThe number of places that get the meaning of DevOps wrong is too high. So much that it is often easier to use it wrong in order to express an idea.
- smeagull 4y agoI do think there is a space for a developer team model that is easy to maintain, hard to screw up and gives say 80% of the productivity gains.