At DevOpsDays Austin 2012, I talked about how devops came about in 2009 by organizing a conference and accidentally coining a word. The concept drew on what already existed – continuous integration, agile, kanban, cloud – but mixed them in a new way.
When asked about the definition of devops, I explained why there is no manifesto. People wanted one, but writing it down would have frozen the idea. By not defining it rigidly, the concept kept growing because everyone could bring their own piece to the table. There are 25 definitions of cloud, and it is still useful. Same thing.
The other point that came up was tools versus culture. I had learned from agile that test-driven development and tooling were crucial, but agile was really about people. Infrastructure as code, continuous integration, and cloud are enablers for faster collaboration and feedback – but having the tool does not mean you will succeed. Tools are the easy part. People are the hard part. Culture makes it effective to drive change in how people think, and then the tools come in to enable that change.
Watch on YouTube – available on the jedi4ever channel
This summary was generated using AI based on the auto-generated transcript.