… unless you are ready to clarify what exactly do you mean by “DevOps”, I suggest you
shut up don’t use that word at all.
The reason not to call a person “DevOps” is that DevOps seems to be a set of principles but not a person nor a job position. None of the amorphous definitions say it’s a person or position so don’t call DevOps anyone please.
Here is why I don’t recommend using this term at all:
- There is no exact definition. I’ve asked several people from in the industry and none of them could define the term precisely.
- Some people think that using specific tools is being DevOps. Some don’t. I don’t. Specific tools can not be used all the time as situations are different.
- Wikipedia has a description which I’m not sure can be used as a definition because some people would agree and some won’t.
- New Relic guys write “First, let’s just say there is no definitive answer.” in the article What is DevOps?.
- Automation seems to be one of the principles. Does it mean that an unsuspecting person that automates processes is now suddenly practicing DevOps? Are we just naming existing practices with a new fancy term now?