在看《Effective DevOps》这本书的时候,前言那里有一段关于devops的拼写的说法。

"Devops", "devops", or "DevOps"?

We have had many discussions over the capitalization(or lack thereof) of the term "devops", A simple online poll showed overwhelming support for "DevOps". We also found a focus on the "Dev" and "Ops" within organizations, This has lead to the creation of "DevSecOps" and "DevQAOps", as "DevOps" implies an exclusivity of just "Dev" and "Ops".

Ultimately, this is why we've chosen "devops" - it reflects the original hashtag on Twitter used to connect people who want to help change conversations from *us versus them* to *enabling the business* with sustainable work practices that focus on people.

Successful projects require input, effort, insight, and collaboration from people across the organization; the problems inherent in your organization may not be limited to just developers and operations team. We have deliberately chosen to use lowercase "devops" throughout the text of this book to reflect our view that this is an inclusive movement, not an exclusive one.

的确,我们每个人都在根据自己的理解在阐述devops这个词了。不过我还是挺认同作者选定使用devops的理由,我们应该是聚焦于业务怎么持续化发展本身而不是谁的责任。成功取决于很多的因素,每个团队或者企业面临的问题都是不一样的,并不是所有的问题都是单纯的DevOps的问题。显然DevOps这个词更容易诱导别人认为这只是DevOps的事情,从而衍生出更多类似DevSecOps或者DevQAOps这样的词出现。

不过作者虽然在书里面使用了devops,但是封面上却使用了DevOps这个拼写,也是挺有趣的一件事情。