What used to be emerging practices in devops have become deep practices – everyone does CI/CD now. The emergent shift is that more people understand the relationship with the business. I have seen many companies over-automate: engineers chant “automation, automation” without asking whether the automation still makes sense versus buying a service. That cost-benefit thinking is an interesting cultural change.
We are also collaborating across companies now, not just within them. You cannot call Amazon when you have a problem the same way you talk to the team down the hall. External providers have become part of our pipeline, and they might be our next bottleneck. That cross-company collaboration is fundamentally different from getting dev and ops to sit together.
COVID proved something important: sitting in the same room was not the only way to collaborate effectively. Open source projects have been doing it remotely for years. Many companies used the crisis as an opportunity to invest in their people through wellness budgets and other support – recognizing that people are the most valuable part of the company.
The devops label still matters. It is a rally cry. Just like the stories around devsecops are going in the same spirit – having that label where you can find good practices, where people want to learn how things are evolving, that is the power of one tag. I coined it by accident in 2009 because “agile system administration conference” was too long. The fact that nobody could trademark it, that it was open, that no single company owned it – that is what let it flourish.
Watch on YouTube – available on the jedi4ever channel
This summary was generated using AI based on the auto-generated transcript.