deep devops - learning to learn dotScale 2017
2 likes1,436 views
The document discusses the principles and practices of DevOps, emphasizing the importance of collaboration between developers and operations, and the need for organizations to build learning environments. It highlights key themes such as automation, culture, and continuous improvement, while critiquing common misconceptions about DevOps tools and practices. The author argues that adaptability and a focus on outcomes are crucial for success in modern software development and operational practices.
deep devops - learning to learn dotScale 2017
- 1. deep devops learning to learn Andrew Clay Shafer @littleidea
- 5. @littleidea
- 6. Agile Infrastructure @littleidea’s greatest hits compilation Change Management There Is No Talent Shortage leading a learning organization
- 7. everyone wants the devops
- 9. where are we? how did we get here?
- 10. Operations is the secret sauce
- 11. you can either easily manage complex systems at scale… or you can’t
- 12. I’ve been using that same slide for the better part of a decade
- 13. fascinated with the dynamics of high performing systems and teams
- 14. same tools, same advice, drastically different results
- 16. what, how and why you automate is as important that you do
- 18. yay automation!
- 19. I’m sure some of you have lived this too or are about to
- 20. yay automation!
- 21. If Tetris Has Taught Me Anything, It’s That Errors Pile Up and Accomplishments Disappear
- 22. why > what
- 23. Pareto Inefficient Nash Equilibria Rule Everything Around You
- 24. Pareto Inefficient - a change benefits someone without detriment to anyone Nash Equilibrium - no one will change
- 25. at a Nash Equilibrium there is no benefit to changing true by definition
- 26. Punctuated Equilibrium evolutionary gradualism is virtually non-existent in the fossil record
- 27. Evolution in the fossil record comes in sudden jumps and extinction events
- 28. Nash Equilibria til death do us part lose if you keep playing the same way
- 29. what is the devops?
- 30. devops • developers and operations can and should work together • system administration evolving to look more like software development • evolving together as global community sharing solutions
- 31. devops - calms • culture • automation • lean • metrics • sharing the five pillars
- 32. optimizing human performance and experience operating software… and humans with software…
- 33. software is changing everything including software and organizations
- 34. you are either building a software business... or you will be losing to someone who is...
- 35. you are either building a learning organization... or you will be losing to someone who is...
- 36. everyone wants the devops Well actually…
- 37. what they really want • scalability • availability • reliability • operability • usability • all for free • without changing anything
- 38. good luck; have fun
- 40. These things are all one…
- 41. continuously devops microservices or die trying
- 42. the patterns proven successful building and operating highly available systems with predictable scaling and failure characteristics
- 43. devops as she is spoken at scale at Google™ not that Google is the best at every possible thing, but where is your book?
- 44. SRE • developers and operations can and should work together • solving system administration with software development • participating in the global community sharing solutions
- 45. SRE - calms • culture • automation • lean • metrics • sharing
- 46. Homework • Embracing Risk • Service Level Objectives • Eliminating Toil Bonus: Communication and Collaboration in SRE
- 47. why > what
- 48. Google is an organization that changes
- 49. who puts as much effort into designing organizations as our computational systems?
- 50. how many of our organizations are able and willing to change?
- 51. how many of us are willing and able to change ourselves?
- 52. You haven’t learned anything until you change your behavior
- 53. The learning organization is one that has the capacity to integrate people and structures in order to move toward continuous learning and change.
- 54. no one originally set out to do devops, continuous delivery, microservices, these were natural consequences don’t fixate on the words, don’t fixate on the tools, fixate on the outcomes
- 55. principles > practices > tools
- 56. mindset > skillset > toolset
- 57. adapt > adopt
- 58. The problem isn’t technical. The problem isn’t people. The problem is socio-technical. We have to solve both together.
- 59. It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is most adaptable to change. — No evidence Darwin ever said this
- 61. my next talk: ’the science of why you shouldn’t change everything at once’ @littleidea
- 62. I don’t hope to have answers I hope to ask better questions @littleidea
- 63. We are uncovering better ways of developing software, by doing it and helping others do it