4 ms·

I also recently wrote a blog post about this, trying to sum up why different definitions exist. https://link.medium.com/tC5p4nfYCib https://link.medium.com/tC5

• dijit 5y ago
  I think it's good that you took the time to write such a detailed post, certainly better than mine in a lot of ways. I agree that Development should be mostly self-service and that the goal of any "Ops" person is to get out of the way. "Automate yourself out of a job" is a common sysadmin mantra. However I don't agree with your other points, there's some over exaggeration when you say "if devops doesn't exist then thats a red flag", if devops can mean anything then it's a useless term and absence of it shouldn't be seen as a red flag. >Shoud DevOps engineer be a role? Yes. Absolutely. Small typo here, and of course I disagree with the statement and preceding paragraph. I think "Platform Engineer" is closer to what your definition of DevOps is. The point of my post is that everyone has their own definition, which is why I'm frustrated at the term. > Infrastructure Engineer Regarding this... This is actually my job title right now, but it exists outside of computing: "Infrastructure Engineer" being the kind of person who makes bridges and roads and so on.
  • bigiain 5y ago
    > "Infrastructure Engineer" being the kind of person who makes bridges and roads and so on. Reminds me of an old old joke. There are two kinds of Engineers. Mechanical Engineers who build weapons, and Civil Engineers who build targets.