5 ms·
I think there's a point to the blog article itself, but i think you miss a vital point in the conclusion. The way a DevOps position that is described in the blo
by Jumziey 5y ago
I think there's a point to the blog article itself, but i think you miss a vital point in the conclusion. The way a DevOps position that is described in the blog post is a valid position that could have DevOps in the title. But that's not usually how the DevOps role is used. This can be easily seen in many listings of the job title.
The analogy with agile is pretty good here. Sure you could have an Agile Engineer, that works primarily with making sure the agile process is actually used and help facilitating that. Normally that would not be a position itself though, especially not an engineering one.
- nhumrich 5y ago> you miss a vital point in the conclusion Never had someone tell me I dont understand my own conclusion to my own article before. Thats a first.
- Jumziey 5y agoYou can certainly misrepresent your own article. But in this case you're arguing different things as far as I interpret your text.
- nhumrich 5y agoMy argument, in both cases, is that devops can be a title, and that the blanket statement "Devops isnt a role", is incorrect. Sure, maybe some job postings are still wrong, but that doesnt mean they are all wrong.