3 ms·
Sure, but if you're hiring people in a different role that does all of the ops work for developers, this isn't "devops". This is just "ops".
by nrmitchi 4y ago
Sure, but if you're hiring people in a different role that does all of the ops work for developers, this isn't "devops". This is just "ops".
- wizofaus 4y agoSounds like a terminology issue then, I consider it "devops" because they're mostly writing code that goes into our git repo etc. etc., they still have to do PRs and code reviews etc. But the code is to handle deployments, not to implement features.
- jen20 4y agoYes: the terminology problem is the is you are using the terminology wrong. DevOps is about cross-functional teams, and has been co-opted by vendors to sell products. And delivery of software is the ultimate feature: without it, nothing of value can be produced.
- wizofaus 4y agoThen everybody else I've worked with over the last 6 or 7 years is also using it wrongly.
- jen20 4y agoQuite likely.
- wizofaus 4y agoWell then we're just getting into debates about what determines the "correct" meanings of word. I read the original article and most of the comments here using my understanding of the term, and it made sense that way...
- wizofaus 4y ago(not to beat a dead horse, but I just finished some interviews I was involved in as an advisor and the term DevOps was used a lot in all of them. And in every single case the term was used exactly the way I've understood to mean - i.e., DevOps engineers are those who primarily look after the CI/CD pipeline, generally don't write application-level code or develop features, but do very much spend the majority of their time developing scripts and tools to enable CI/CD).