3 ms·
> There is no single definition, rather people use the term ‘DevOps’ as it suits them. And I don’t see harm in doing that as long as the basic concept is clear.
by twic 10y ago
> There is no single definition, rather people use the term ‘DevOps’ as it suits them. And I don’t see harm in doing that as long as the basic concept is clear.
That's the thing, though - the basic concept very obviously isn't clear.
I've seen it go from "developers automating what operators do" to "developers and operators working together" to "operators using automation" to "operators doing things manually" to, in this article, "developers or operators doing things however".
There isn't really much point in using a term with such loose and varying meaning.
- tibu 10y agoHow about "developers taking responsibility of their own code in live environment"?
- twic 10y agoI forgot that one! I guess that was an alternative branch from "developers automating what operators do", which implies a degree of that. Only instead of automating, they just do what the operators do now.
- schainks 10y agoThis highly depends on the nature of your organization and how many developers you're dealing with. I've seen it quickly break down once you reach more than 3 products and more than 15 devs. Otherwise, at some point, you need a group of people (devs or otherwise) to sit down, define how these things are done for everyone, get group buy-in, then build the thing that puts their things in live environment.
- quintes 10y agoI've even seen it used to describe the support team who really just fix the bugs and get the changes into prod by some means... Not my Definition but something I've seen.