Skip to content

From Dev/Ops to DevOps - Patrick Debois and Kris Buytaert

talks 2 min read

The classic scenario: developers write code, deadline approaches, they throw it over the wall to operations, and the fighting begins. Ops asks for deployment details, monitoring requirements, database configurations, expected load. Dev says “put it in production now, it is the biggest marketing thing.” Both sides optimize for their own silo, and the business suffers.

The first breakthrough is infrastructure as code. With virtualization and cloud, we went from managing 10 machines to thousands – and you cannot do that one by one. Tools like Puppet and Chef let you define infrastructure in code: version-controlled, testable, rebuildable from scratch. You can throw a machine out of the tenth floor and be back up in no time. But automation alone is not enough. You still need the human collaboration.

From the agile side, operations can borrow practices like planning poker for estimating work, Kanban boards for visualizing flow and finding bottlenecks, and pair working for knowledge transfer. The key insight: flow-based work handles interruptions (incidents) better than fixed sprints for ops teams. Limiting work in progress prevents deadlocks when too many tasks pile up at one stage.

Continuous integration for infrastructure means rebuilding your environment over and over, combining software releases with infrastructure releases, and deploying that combined artifact to production. It is not about the number of deploys per day – it is about reducing cycle time and building confidence. The hard part is not technical. It is cultural: getting management to think in terms of business value rather than local optimization, convincing developers and ops that they share the same customer, and recognizing that the cron job fix in production is actually technical debt that needs to go on the backlog. DevOps is about culture, automation, measurement, and sharing. The tools are easy. Changing how a company thinks and behaves – that is the difficult step.

Watch on YouTube – available on the jedi4ever channel

This summary was generated using AI based on the auto-generated transcript.

Navigate with