Jesse Robbins on the Rise of DevOps (InfoQ Interview)

In this January 2013 InfoQ interview, Harry Brumleve talks with Jesse Robbins about the transition from traditional operations to DevOps culture, infrastructure as code, and how the organizational changes that enabled Amazon’s scale could be made available to everyone else.

DevOps as a Culture Shift, Not a Tool

InfoQ’s description of the interview frames the central argument: “Jesse Robbins of Opscode discusses how the concept of deploying, maintaining, and updating a software solution has begun to evolve into the concept of DevOps. This new player in the development landscape blurs the lines between Development and Operations teams and creates a new practice of Infrastructure as Code.”

DevOps wasn’t a software category — it was a reorientation of how organizations thought about building and running software. The walls between development teams (who wrote code) and operations teams (who ran it) weren’t just organizational silos; they were failure modes, points where accountability broke down and blame accumulated instead of improvement. At Amazon, operations had been treated as a source of competitive advantage rather than a cost center. The question in 2013 was how to make that culture replicable beyond the hyperscalers.

Infrastructure as Code: The Programmatic Shift

By 2013, Chef — the open-source tool Robbins had built with Opscode — was the clearest embodiment of what infrastructure as code meant in practice. Servers weren’t machines to configure manually; they were instances of a declared state that code could create, modify, and destroy. The same version control, testing, and review workflows that software teams used for applications could now apply to infrastructure.

The implications were significant. Infrastructure became auditable, reproducible, and collaborative. A change to a server configuration was now a pull request, not a undocumented action by a sysadmin at 2am. Teams could deploy infrastructure the way they deployed code — with confidence that the outcome would match what was specified.

Velocity and the Community That Made DevOps Real

Velocity, co-founded in 2007, was a conference where fierce competitors — Google, Amazon, Microsoft — shared what they knew about running complex systems reliably. The practitioners who gathered there developed a shared vocabulary, shared standards, and shared intuitions about what good operations looked like. By 2013, that community had grown into a movement with its own name.