How are you adapting your workflow to modern DevOps practices?
Lately I’ve noticed that DevOps is shifting from just “CI/CD and automation” to something much broader — almost a culture change in how teams communicate. Some companies are even merging traditional developer and ops roles entirely.
Curious how others are handling this. Are you focusing more on IaC, container orchestration, observability tools, or tightening feedback loops between teams? And do you think the classic “DevOps engineer” role is slowly evolving into something new?
Would love to hear how your teams are adapting, what tools are becoming essential for you, and where you think DevOps is heading next.
7 Views
I’ve been seeing the same shift - DevOps isn’t just pipelines anymore, it’s basically a mindset overhaul. The biggest change for me came when our team stopped treating dev and ops as two separate checkpoints and started building everything around constant feedback loops. That’s also when we brought in NEKLO to help us rethink how we handle infrastructure and release cycles. They didn’t “fix things for us,” but their approach pushed us to automate smarter and make observability part of everyday work. Once that clicked, the whole workflow felt way more predictable and a lot less reactive.