[solatic]

Great DevOps practitioners are rarer than 10x engineers. It's the combination of:

* Systems knowledge through the lens of Conway's Law: what does an ideal even look like in terms of organizational efficiency

* Leadership to get disparate teams in an organization to cooperate instead of compete

* Technical competency to help disparate teams adopt the principles, because telling people on the fence to "go Google it" is a plan for failure

People who get bogged down in CI/CD/IaC/containerization miss the forest for the trees and it's why most organizations never see any value out of their DevOps initiatives. If you don't know what to automate then WIP increases your costs. If you don't have leadership on board then you can't reorganize teams to prevent "cycles" and re-work inside the "factory". If you don't have technical competency then you have people re-inventing the wheel, poorly.

You need all three.

[freehunter]

At my day job I have a "devops" guy who is all-in on "devops". By which I mean he wants everything run through a CI/CD workflow, committed into change control, with passing unit tests, and tasks passing through a Jenkins pipeline.

Did I mention we are information security consultants and work in neither dev nor ops? Yeah he wants our powerpoint slides checked into change control. I'm not joking.

[mixmastamyk]

I put docs in vcs, it is convenient. But, binary formats are less useful.

[pts_]

At least put it in a CMS. Managing docs is so absent in workflows.