![- Spread the knowledge
[GREEN] DevOps Service Recovering…](https://image.slidesharecdn.com/army-of-n-160705185632/85/DevOps-Army-of-N-Recovering-From-Being-A-Human-SPOF-37-320.jpg)
![- Spread the knowledge
- Written docs, info sessions, camp out at my desk
[GREEN] DevOps Service Recovering…](https://image.slidesharecdn.com/army-of-n-160705185632/85/DevOps-Army-of-N-Recovering-From-Being-A-Human-SPOF-39-320.jpg)
![- Spread the knowledge
- Written docs, info sessions, camp out at my desk
- We have a team, now, so use it!
[GREEN] DevOps Service Recovering…](https://image.slidesharecdn.com/army-of-n-160705185632/85/DevOps-Army-of-N-Recovering-From-Being-A-Human-SPOF-40-320.jpg)
![- Spread the knowledge
- Written docs, info sessions, camp out at my desk
- We have a team, now, so use it!
- Make sure the entire team is in the loop
[GREEN] DevOps Service Recovering…](https://image.slidesharecdn.com/army-of-n-160705185632/85/DevOps-Army-of-N-Recovering-From-Being-A-Human-SPOF-41-320.jpg)
![- Spread the knowledge
- Written docs, info sessions, camp out at my desk
- We have a team, now, so use it!
- Make sure the entire team is in the loop
- Review what was built and change as needed
[GREEN] DevOps Service Recovering…](https://image.slidesharecdn.com/army-of-n-160705185632/85/DevOps-Army-of-N-Recovering-From-Being-A-Human-SPOF-42-320.jpg)
DevOps Army of N - Recovering From Being A Human SPOF
- 1. DevOps Army of N Jonathan Disher
- 2. - Senior Principal DevOps Engineer, ODC EHLO jon
- 5. - Senior Principal DevOps Engineer, ODC - I do love me some fountain pens EHLO jon
- 7. - Senior Principal DevOps Engineer, ODC - I do love me some fountain pens - Still wrenching on the Miata EHLO jon
- 8. Presentation Title Author or Subtitle Which way to the datacenter?! Image by Dito Milan, GotBlueMilk Photography
- 9. - Senior Principal DevOps Engineer, ODC - I do love me some fountain pens - Still wrenching on the Miata - Still putting Latin on business cards EHLO jon
- 11. - Senior Principal DevOps Engineer, ODC - I do love me some fountain pens - Still wrenching on the Miata - Still putting Latin on business cards - Former Single Point of Failure EHLO jon
- 12. At devopsdays SV in November, I gave a talk about my experiences being a Human Single Point of Failure. Video and slides available on Youtube and SlideShare! DevOps Army of One
- 13. 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 Hosts Engineers November 2015 - It was just me.
- 15. New Year brings Andrew! 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 2/16 Hosts Engineers
- 17. Alex in March… 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 2/16 Hosts Engineers
- 19. and Kimberly in May! 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 2/16 5/16 Hosts Engineers
- 21. hopefully engineer #5 soon! 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 2/16 5/16 Hosts Engineers
- 23. we’re hiring! DevOps, DBA, Big Data… 0 1.5 3 4.5 6 0 625 1250 1875 2500 11/12 2/13 5/13 8/13 11/13 2/14 5/14 8/14 11/14 2/15 5/15 8/15 11/15 2/16 5/16 Hosts Engineers
- 24. Return of the poll: How many of you are now, or have previously, worked in DevOps groups of size == 1? (Specifically where the group was, at one time, size > 1, and shrank to 1)
- 25. Return of the poll: How many of you are now, or have previously, worked in DevOps groups of size == 1? (Specifically where the group was, at one time, size > 1, and shrank to 1) (In November, it was 15-20%)
- 26. Return of the poll: How many of you are now, or have previously, worked in DevOps groups of size == 1? (Specifically where the group was, at one time, size > 1, and shrank to 1) (In November, it was 15-20%) (ouch.)
- 27. So you’ve hired some people…
- 28. So you’ve hired some people… now what?
- 30. - I’ve forgotten how to teach other engineers Being solo had some bad side effects…
- 31. - I’ve forgotten how to teach other engineers - Too many doc sources still say “Go talk to Jon” Being solo had some bad side effects…
- 32. - I’ve forgotten how to teach other engineers - Too many doc sources still say “Go talk to Jon” - Too accustomed to not delegating tasks Being solo had some bad side effects…
- 33. - I’ve forgotten how to teach other engineers - Too many doc sources still say “Go talk to Jon” - Too accustomed to not delegating tasks - People got used to everything being P1 Being solo had some bad side effects…
- 34. - I’ve forgotten how to teach other engineers - Too many doc sources still say “Go talk to Jon” - Too accustomed to not delegating tasks - People got used to everything being P1 - Quality, complete documentation Being solo had some bad side effects…
- 35. - I’ve forgotten how to teach other engineers - Too many doc sources still say “Go talk to Jon” - Too accustomed to not delegating tasks - People got used to everything being P1 - Quality, complete documentation - Sometimes I still feel like I’m in solo crisis mode Being solo had some bad side effects…
- 37. - Spread the knowledge [GREEN] DevOps Service Recovering…
- 39. - Spread the knowledge - Written docs, info sessions, camp out at my desk [GREEN] DevOps Service Recovering…
- 40. - Spread the knowledge - Written docs, info sessions, camp out at my desk - We have a team, now, so use it! [GREEN] DevOps Service Recovering…
- 41. - Spread the knowledge - Written docs, info sessions, camp out at my desk - We have a team, now, so use it! - Make sure the entire team is in the loop [GREEN] DevOps Service Recovering…
- 42. - Spread the knowledge - Written docs, info sessions, camp out at my desk - We have a team, now, so use it! - Make sure the entire team is in the loop - Review what was built and change as needed [GREEN] DevOps Service Recovering…
- 43. So we sat down and did a thorough review of our environment.
- 45. So we sat down and did a thorough review of our environment. We were brutally honest.
- 46. And we’re going to burn a lot down.
- 47. Phoenix Rising
- 48. - We’re rebuilding large portions of infrastructure. Phoenix Rising
- 50. - We’re rebuilding large portions of infrastructure. - Along the way we will build it better, with more review and more modern ideas. Phoenix Rising
- 55. - We will be rebuilding large portions of infrastructure. - And along the way we will build it better, with more review and more modern ideas. - EMPHASIS ON WE - since it’s not just me, information gets shared! Phoenix Rising
- 56. We don’t want angry panda.
- 57. - Periodic cross-team architecture review How can we keep this from happening again?
- 59. - Periodic cross-team architecture review. - Write good documentation, keep it current. How can we keep this from happening again?
- 60. - Periodic cross-team architecture review. - Write good documentation, keep it current. - Keep hiring people. Keep training people. How can we keep this from happening again?
- 61. - Periodic cross-team architecture review. - Write good documentation, keep it current. - Keep hiring people. Keep training people. - Remember saying no? Thats still allowed. How can we keep this from happening again?
- 62. - Periodic cross-team architecture review. - Write good documentation, keep it current. - Keep hiring people. Keep training people. - Remember saying no? Thats still allowed. - Take a vacation. Stay fresh! How can we keep this from happening again?
- 63. Don’t let this be you.
- 64. And we don’t want Phoenix Re-Rising 2020
- 65. Coming Soon!
- 66. Coming Soon! (devopsdays SV 2018?)
- 67. Coming Soon! DevOps Army of N+1 (devopsdays SV 2018?)
- 68. Coming Soon! DevOps Army of N+1 Achievement Unlocked: Team Redundancy! (devopsdays SV 2018?)