If Coca-Cola had invented DevOps, the early days would look familiar: it is a cure for everything – mental exhaustion, physical exhaustion, even pregnancy. Delivery? Yay, continuous delivery, driving the truck. Communication, collaboration, culture – we keep talking and talking about it. Automation makes it consistent: every bottle tastes the same, every deploy is reproducible. “A million deployed today” becomes the boast.
The sharing and pairing is the cozy family feeling. Then come the blind taste tests – are you deluding yourself that your approach actually tastes better? No-ops is sugar-free. Infra-coders call themselves DevOps but only care about the tools. Vendors say “me too” and start labeling their products as DevOps. It becomes semi-addictive: more tools, more stuff, and you relax because “we have a DevOps tool so we are DevOps.”
Fanboys emerge for every religion – Chef vs Puppet vs whatever – and designer consultants appear with DevOps in their job title. Reports and surveys make you believe this will solve your problems. But here is the point: if you are in your company and silos are not talking to each other, you have to find your own bottleneck. Not the one someone else tells you is the problem. Learn from your own mistakes. And after four years of living in this world, the main message: do not take it too seriously. Adapt it to your needs. Solve your own bottleneck. That is the only recipe that matters.
Watch on YouTube – available on the jedi4ever channel
This summary was generated using AI based on the auto-generated transcript.