DevOps engineers fly from job to job doing the same things - the systems differ, but the problems (technical and otherwise) remain the same. Eventually, we ask questions not about implementation or technology, but meaning: what am I doing all of this for?
In this talk, we'll cover how we provided a converged solution (Docker cluster, monitoring, alerting, and security) from 0 to 70% of the company in three months. We'll cover how we did it - the approaches, the workflows, and the rules - but more importantly, the why: to provide an environment where the things that we produce change whole organizations and make people's lives a little better.
But most of all, how it made us a little bit kinder.
The future is going to be weird: technologies are growing faster than we can teach them, and we need more experts quick. In this talk, we'll discuss the many ways we teach DevOps practices in an organization as analogues of how systems transmit data. We'll talk about the advantages and pitfalls of:
- Broadcast systems (e.g., Universities) - 1:1 Discovery (e.g., Mentorships) - Gossip protocols (e.g., Communities and guilds)
We'll unpack each methodology, discuss the information dispersal mechanisms and attributes of each system, and see where they fit. Because really: DevOps isn't about technology choice, or language, or infrastructure. First and foremost, it's about people.