DevOps - Keepers of the Keys to the Kingdom


Published on

Ben Kepes of Clouderati fame joined us for the first ever DevOps conference in Israel - and spoke about the driving force behind DevOps in organizations today.

Presented at DevOps Con Israel 2013

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

DevOps - Keepers of the Keys to the Kingdom

  1. 1. DevOpsCon Israel @benkepes Diversity Limited January 2013 DevOps – Keepers of the Keys to the Kingdom
  2. 2.
  3. 3.
  4. 4.
  5. 5.
  6. 6. The world is changing – fuelled by underlying trends
  7. 7.
  8. 8. “Fast and frequent feedback is what allows fordevelopers to be productive. Developers hate being bored.” - John Allspaw, Etsy
  9. 9.
  10. 10.
  11. 11. “Code that has been written but not yet deployed is very similar to inventory, you’ve paid the cost to develop the software but are not yet getting any of the benefit from it” - Mark Imbriaco, GitHub
  12. 12.
  13. 13.
  14. 14. Maggie Osama
  15. 15. “This extremely high level of automation and the work practices that go with it, together offer a revolutionary step-change in the way that we engineer complex systems:- a revolution that companies like Google and Netflix have embraced; a revolution that the rest of us ignore at our peril.” - WT Payne, outage-is-a-sign-of-things-to-come
  17. 17. “Systems that contain and absorb many smallfailures without breaking and get more resilient over time are ‘antifragile’… We actively try tobreak our systems regularly so we find the weakspots… as a result we tend to survive large-scale outages better than more fragile services.” - Adrian Cockcroft, Netflix
  18. 18. Maggie Osama
  19. 19.
  20. 20.
  21. 21. • Talk about the uber democratization of pgrogramming – citizen programmers – citizen ops – citizen outcomes. Ref my blog post
  22. 22. jamesjyu
  23. 23.
  24. 24. Developers (and the Business) are Frustrated
  25. 25. The Business Wants (and Needs) New Stuff
  26. 26.
  27. 27.
  28. 28.
  29. 29.
  30. 30. “Every developer must think of the end user. Committing a piece of code is far from being done. It needs to work in all kinds of weird use cases. And it’s not only QA’s job to find all the bugs. Good developers want to ensure that the new features are not only coded, but tested and ultimately released to their users. Only then the task is really done.” - Matthias Marschall
  31. 31. “Having a nice script on your own box is not enough. Every sysadmin needs to make sure it’s possible to re-create each part of the infrastructure at any time. When that slick, new script is under version control, written in a way others can understand and modify it, is their task really Done.” - Matthias Marschall
  32. 32. Think like a team
  33. 33. “DevOps teams do not run under the constraint of individual profiles. They have to take broader responsibilities: everyone needs to care about getting valuable features into the hands of their users, and everyone should pro- actively find ways to contribute to the solution of any release blocker, no matter what the problem is. They work with ‘Us’ spirit rather than ‘Them/their’.” - Isha Suri
  34. 34.
  35. 35. “…QA among the developer teams can ensurebetter code performance by having a stringent focus on code issues and those related to the general site reliability. Plus, by being moreoperationally aware of the production contextthat our code lives within, developers can also design and build better software.” - Isha Suri
  36. 36.
  37. 37. “…this is possible only by increasingcommunication with operations teams willwe developers learn about these concernsand incorporate them into our designs and every day coding decisions.” - Isha Suri