While the job does deal heavily in automating things, it only automates Boolean things. Looking at a platform and seeing why and where it’s failing is not a Boolean thing, and never will be. It’s the same reason we still don’t have machines that repair cars over 100 years after their introduction.
Okay bud, go and tell AWS, Google, Salesforce, and any other of these companies who think “AI” is an answer to everything, because they’ve all had very public outages due to this exact same thing in the past few months.
You have no idea what DevOps is or how it works if you think any of this is easily done or solved with these junk tools.
Been running Ops teams for decades, kid. Look at alllll the people agreeing with me, and disagreeing with you. You have the unearned wisdom of a struggling Junior Dev. If you had any experience, you’d know how embarrassing it would be to attempt to brag about working for “multi-billion dollar companies” 🤣🤣🤣🤣
Yes, those big, big companies are where ALL the good engineering jobs are at. Where all the interesting work is being done 🤣🤣🤣🤣
If you think that DevOps isn’t one of the most automated parts of software then you’re doing DevOps very wrong. Do you do manual builds and deployments every single time? No CI/CD?
You are not reading or understanding comments, child. That’s not what I said whatsoever.
You’re of the opinion that DevOps engineers can be automated away. I proved you wrong. Now you’re talking about the tooling, which is in my first comment to you. Automated tooling is NOT all DevOps is, and the fact you think shows me you’re unseasoned in whatever it is you do, have no concept of the role.
It would be people like you who would not pass the first round of interviews from answering a question about this topic exactly as you’ve stated, because you don’t understand the core function of the team, and you’re role in it.
You make some code, and obviously have no idea how to run it, let alone at scale. All the working pieces of a platform at large need to be understood and vetted by a DevOps team in order to make it run, and run well. That’s understanding everything from start to finish, in ways you wouldn’t be able to comprehend being one part of team that is building one part of a platform. You can’t make an agent that understands all the underpinnings of all the services or metrics, and why they fail, that then takes action on them, because it’s not something AI does. Case in point, the AWS outage and others I mentioned.
Now, you could make MANY agents that take actions on many things, but that doesn’t give situational awareness or comprehension to any singular agent, something AI also doesn’t do. That’s what DevOps teams do.
I don’t even need to keep arguing with you about this, because the down votes on your comments speak for themselves. I’m just trying to educate on your false understanding about how it all works so you don’t stumble through your career making the same comments and mistakes.
Exactly. DevOps engineers are already super skilled at using automation where appropriate, but knowing how and when to do that is still an extremely human task
…noooooo, it most definitely isn’t.
While the job does deal heavily in automating things, it only automates Boolean things. Looking at a platform and seeing why and where it’s failing is not a Boolean thing, and never will be. It’s the same reason we still don’t have machines that repair cars over 100 years after their introduction.
AI can see why and where it’s failing too if it has the appropriate permissions and access.
No it’s not. DevOps is all software, repairing cars is not. Car ECUs can tell you exactly what is wrong with your car.
🤣
Okay bud, go and tell AWS, Google, Salesforce, and any other of these companies who think “AI” is an answer to everything, because they’ve all had very public outages due to this exact same thing in the past few months.
You have no idea what DevOps is or how it works if you think any of this is easily done or solved with these junk tools.
AI in devops caused their outages?
Do you even know what Octopus is for example? Azure DevOps?
Again, refer to my first comment because you’re out of your league here 🤣🤦
Already replied to that and showed why you’re wrong.
I do DevOps and Software Dev for multi-billion dollar companies btw.
Been running Ops teams for decades, kid. Look at alllll the people agreeing with me, and disagreeing with you. You have the unearned wisdom of a struggling Junior Dev. If you had any experience, you’d know how embarrassing it would be to attempt to brag about working for “multi-billion dollar companies” 🤣🤣🤣🤣
Yes, those big, big companies are where ALL the good engineering jobs are at. Where all the interesting work is being done 🤣🤣🤣🤣
My GAWD, child. W O W 🤦
Nice try but no cigar.
If you think that DevOps isn’t one of the most automated parts of software then you’re doing DevOps very wrong. Do you do manual builds and deployments every single time? No CI/CD?
You are not reading or understanding comments, child. That’s not what I said whatsoever.
You’re of the opinion that DevOps engineers can be automated away. I proved you wrong. Now you’re talking about the tooling, which is in my first comment to you. Automated tooling is NOT all DevOps is, and the fact you think shows me you’re unseasoned in whatever it is you do, have no concept of the role.
It would be people like you who would not pass the first round of interviews from answering a question about this topic exactly as you’ve stated, because you don’t understand the core function of the team, and you’re role in it.
You make some code, and obviously have no idea how to run it, let alone at scale. All the working pieces of a platform at large need to be understood and vetted by a DevOps team in order to make it run, and run well. That’s understanding everything from start to finish, in ways you wouldn’t be able to comprehend being one part of team that is building one part of a platform. You can’t make an agent that understands all the underpinnings of all the services or metrics, and why they fail, that then takes action on them, because it’s not something AI does. Case in point, the AWS outage and others I mentioned.
Now, you could make MANY agents that take actions on many things, but that doesn’t give situational awareness or comprehension to any singular agent, something AI also doesn’t do. That’s what DevOps teams do.
I don’t even need to keep arguing with you about this, because the down votes on your comments speak for themselves. I’m just trying to educate on your false understanding about how it all works so you don’t stumble through your career making the same comments and mistakes.
Exactly. DevOps engineers are already super skilled at using automation where appropriate, but knowing how and when to do that is still an extremely human task