Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Pe

10+ deployments per day from Velocity 2009. It was really a pivotal talk in the early days of the DevOps movement [this video] Fixing Twitter: Improving the Performance and Scalability of the World's Most Popular Micro-blogging Site by John Adams (then from Twitter)at Velocity 2009 (Velocity 2009 was really an incredibly pivotal and influential conference in the DevOps movement). [link] Bootstrapping an Infrastructure by Steve Traugott at Lisa 1998. I don't know of any videos of the talk, but the related paper eventually lead to Puppet and the beginning of the modern configuration management software [link] There is no talent shortage by Andrew Schaefer, co-founder of Puppet from Velocity NYC 2013. [link] (edited for consistant formatting)

People downvoting this guy are misinformed. There are two major sources for DevOps: 1) the 10+ deploys a day talk from Flickr: [this video] which is where most of the actual methodology comes from. 2) The "DevOps Days" (first use of the portmanteau by Patrick Dubois) which was an agile conference aimed at Systems Administrators trying to get them to work more agile; the conference was called "DevOps" to make developers think it was also for them. Neither of these primary sources said that we should erode or replace ops people; or that it was ever intended to be a role or individual responsibility. This is a lie that corpo's have made to reduce headcount.

You've decided your definition, as many have. DevOps as written is not what you're saying; this has been mentioned at least 20 times in this thread. Sysadmins of yore were developers, they used perl and C and eventually ruby. Then there was a glut of sysadmins who couldn't code, then people acquired collective amnesia that sysadmins ever coded and invented a new term. The issue was that the term that they decided to use for this new breed of developer operations folk was the same word that was used for a methodology of breaking down siloes (having developers and operations as distinct entities but working together)[0] and the same word that was being used to describe sysadmins adopting Agile[1]. The annoying thing about the passage of time is that you look back and see only what has changed and may conclude that those changes are a result of paradigm shifts: you could be right, but sysadmins were using proto versions of common paradigms now: version control integrations used to be bad and fragmented, but it was ops pushing VCS; infrastructure as code via cfengine; cluster management with clustered ssh clients (cssh). I was there, I saw this. It's hard to differentiate between the slow march of progress of operations tooling (rebranded as devops tooling) and the fact that it might not actually be linked to devops as a methodology. [0]: [this video] [1]: [link]