Downloaded 16 times
Uploaded byAndrew Shafer
deep devops - learning to learn dotScale 2017
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.
More Related Content
Similar to deep devops - learning to learn dotScale 2017
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
deep devops - learning to learn dotScale 2017
- 1. deep devops learning tolearn Andrew Clay Shafer @littleidea
- 2.
- 3.
- 4.
- 5.
- 6. Agile Infrastructure @littleidea’s greatest hits compilation ChangeManagement There Is No Talent Shortage leading a learning organization
- 7. everyone wants thedevops
- 9. where are we? howdid we get here?
- 10. Operations is thesecret sauce
- 11. you can eithereasily manage complex systems at scale… or you can’t
- 12. I’ve been usingthat same slide for the better part of a decade
- 13. fascinated with thedynamics of high performing systems and teams
- 14. same tools, sameadvice, drastically different results
- 16. what, how andwhy you automate is as important that you do
- 18.
- 19. I’m sure someof you have lived this too or are about to
- 20.
- 21. If Tetris HasTaught Me Anything, It’s That Errors Pile Up and Accomplishments Disappear
- 22.
- 23. Pareto Inefficient NashEquilibria Rule Everything Around You
- 24. Pareto Inefficient -a change benefits someone without detriment to anyone Nash Equilibrium - no one will change
- 25. at a NashEquilibrium there is no benefit to changing true by definition
- 26. Punctuated Equilibrium evolutionary gradualismis virtually non-existent in the fossil record
- 27. Evolution in thefossil record comes in sudden jumps and extinction events
- 28. Nash Equilibria til deathdo us part lose if you keep playing the same way
- 29. what is thedevops?
- 30. devops • developers andoperations 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 performanceand experience operating software… and humans with software…
- 33. software is changingeverything including software and organizations
- 34. you are eitherbuilding a software business... or you will be losing to someone who is...
- 35. you are eitherbuilding a learning organization... or you will be losing to someone who is...
- 36. everyone wants thedevops Well actually…
- 37. what they reallywant • scalability • availability • reliability • operability • usability • all for free • without changing anything
- 38.
- 39.
- 40.
- 41.
- 42. the patterns provensuccessful building and operating highly available systems with predictable scaling and failure characteristics
- 43. devops as sheis spoken at scale at Google™ not that Google is the best at every possible thing, but where is your book?
- 44. SRE • developers andoperations 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.
- 48. Google is anorganization that changes
- 49. who puts asmuch effort into designing organizations as our computational systems?
- 50. how many ofour organizations are able and willing to change?
- 51. how many ofus are willing and able to change ourselves?
- 52. You haven’t learnedanything until you change your behavior
- 53. The learning organizationis one that has the capacity to integrate people and structures in order to move toward continuous learning and change.
- 54. no one originallyset 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.
- 58. The problem isn’ttechnical. The problem isn’t people. The problem is socio-technical. We have to solve both together.
- 59. It is notthe 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
- 60.
- 61. my next talk: ’thescience of why you shouldn’t change everything at once’ @littleidea
- 62. I don’t hopeto have answers I hope to ask better questions @littleidea
- 63. We are uncoveringbetter ways of developing software, by doing it and helping others do it