,
14 tweets,
2 min read
Read on Twitter
Confession: I don't get "DevOps", a thread. 1/14
I've read The Phoenix Project and the DevOps Handbook, and I still don't really get it. 2/14
Some people use DevOps to mean something akin to "programming infrastructure and ops automation", usually synonymous with config management tools like Puppet/Chef/Ansible/Salt. See "Devops Engineer" positions. 3/14
But the typical response to this sort of thing is: "No, DevOps is *really* about culture and interaction among teams". I still don't really get this. 4/14
The culture part sounds to me like, "You should have an organizational culture where there's incentives and goals are well aligned across teams". 5/14
I mean, I agree with that, but why does that need a movement with a name? That just sounds to me like "You should have a healthy organizational culture". 6/14
It might be that I've simply never worked in a company that suffered from the problems that the DevOps movement arose to address. 7/14
My first job out of university was a five(?)-person startup. (They're still around! Hi @XiposSystems!). 8/14
(Then it was grad school and working as an assistant professor for a couple of years). 9/14
Then I went to work for a research lab (@USC_ISI). The researchers were responsible for managing the bare-metal hardware. We ran (and contributed to) OpenStack. 10/14
Then, another startup (They're also still around! Hi @NimbisSvcs!). 11/14
Then I worked for SendGrid. But I was part of SendGrid Labs, which operated much like a startup. 12/14
And, finally, Netflix, which has a strong "you build it, you run it" culture. 13/14
So, I've never experienced the problems of those who work in the enterprise space. But DevOps-as-culture always feels to me like "avoid organizational culture pathologies!". Fin 14/14
