← About Jesse Robbins

The DevOps origin story

The DevOps movement did not start with a manifesto or a conference talk. It started in a blog comment thread.

In October 2007, I published “Operations Is a Competitive Advantage” on O’Reilly Radar. I argued that operations was not a cost center. It was a competitive advantage and occasionally a strategic weapon. Luke Kanies showed up in the comments and introduced me to Adam Jacob. John Allspaw weighed in from Flickr. John Willis talked about EC2. The people who would build the movement were already arguing about infrastructure before anyone called it DevOps.

That same year, Steve Souders, Brady Forrest, Artur Bergman, and I walked into Tim O’Reilly’s office and said “we need a gathering place for our tribe.” Tim said yes. That became the Velocity Conference. I had lived the problem at Amazon, where operations teams always missed the launch party because we were too busy in the data center trying to support a launch. Velocity was the answer: bring the practitioners together and let the ideas compound.

They compounded fast. By 2009, John Allspaw and I were on stage at Velocity laying out the art of web operations. In 2010, we co-edited Web Operations, the O’Reilly book that defined the field, with essays from practitioners at Amazon, Google, and other companies doing this work firsthand. That same year, I co-organized the first US-based DevOps Days in Mountainview with Damon Edwards, Andrew Shafer, and John Willis.

Meanwhile, I had been running GameDay exercises at Amazon since 2004, deliberately injecting failures into production to build organizational resilience. That work pioneered what people now call chaos engineering, incident management, and site reliability engineering. In 2012, Kripa Krishnan from Google, John Allspaw from Etsy, and I published “Resilience Engineering: Learning to Embrace Failure” in ACM Queue, describing how we built organizations that deliberately trigger failure to get stronger.

Luke Kanies’s comment on that 2007 post introduced me to Adam Jacob. That introduction led to Chef. I cofounded Chef to put the “infrastructure as code” part of DevOps into practice as open-source software. Chef gave every team the same infrastructure automation capabilities that had been closely guarded secrets at Google and Amazon. Hundreds of incredible people built that company. The tools mattered. The movements they created mattered more.

John Willis later traced the three threads that created DevOps and named that 2007 post as one of them. His verdict: “Without Patrick, John, and Jesse, the DevOps movement may have never gained the traction necessary to really take off.” DevOpsANGLE independently reached a similar conclusion.

The community that grew out of Velocity created something that outlasted any single company or tool. It created #hugops, a culture of empathy for the people who keep the internet running. It created career paths where none existed. It changed how the best engineering organizations work.

I kept 179 archived web pages from those years. Blog posts, conference writeups, comment threads, press coverage. In 2025, I used AI developer tools to process the archive and recover the story you can read across the mentions linked below.

Further Reading