$30 off During Our Annual Pro Sale. View Details »

Passing the Console: Fostering the Next Generation of Ops Professionals

Passing the Console: Fostering the Next Generation of Ops Professionals

Where does one go to learn ops? There are no sysadmin degrees or operations bootcamps. We learn our trade like dark witches, through varied and arcane means: books, talks, hands-on experiences, real-life outages, and backchannel lore. But tech is a thriving industry, ripe for eager new ops professionals and ideas. You have very likely met the person or people who will follow in your footsteps. So, how do we pass on our craft?

This talk will explore what it means to be in operations and how to pass on that unique skill set. We will discuss what tools and culture define our field, who to pass this knowledge onto, and how to do this effectively. Believe it or not, you are capable of contributing to the greater ops legacy in a variety of ways.

Come learn how to pass the torch—or console—and prepare the next generation of ops.

Alice Goldfuss

December 08, 2016
Tweet

More Decks by Alice Goldfuss

Other Decks in Technology

Transcript

  1. PASSING THE CONSOLE
    Fostering the Next Generation of
    Ops Professionals
    Alice Goldfuss @alicegoldfuss

    View Slide

  2. Hello! I’m Alice.
    I’m an SRE with
    too much free
    time.

    View Slide

  3. Operations

    View Slide

  4. Operations
    Software Engineer

    View Slide

  5. Operations
    Tech Support
    Software Engineer

    View Slide

  6. Film

    View Slide

  7. “Expert” ->

    View Slide

  8. Questions for
    the Audience

    View Slide

  9. Dev

    View Slide

  10. Dev

    View Slide

  11. Dev

    View Slide

  12. Dev

    View Slide

  13. Ops

    View Slide

  14. Ops

    View Slide

  15. Ops

    View Slide

  16. Ops

    View Slide

  17. Why?

    View Slide

  18. View Slide

  19. View Slide

  20. #serverless
    #NoOps

    View Slide

  21. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  22. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  23. Tools Culture

    View Slide

  24. Tools

    View Slide

  25. View Slide

  26. View Slide

  27. View Slide

  28. View Slide

  29. Your tools don’t matter

    View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. Culture

    View Slide

  34. View Slide

  35. LOL

    View Slide

  36. BEWARE OF BOFH

    View Slide

  37. View Slide

  38. Be curious

    View Slide

  39. • What’s this log message mean?
    • How does this protocol work?
    • Who is this user on my system?

    View Slide

  40. View Slide

  41. Build strong systems

    View Slide

  42. • What if we need to failover
    the database?
    • What if the cron job fails?
    • What if we get a spike in
    traffic?

    View Slide

  43. View Slide

  44. Serve your users

    View Slide

  45. • Keep things patched
    • Work with them on dev goals
    • Build automated infrastructure
    to take yourself out of the
    equation

    View Slide

  46. • Protect them from themselves

    View Slide

  47. View Slide

  48. View Slide

  49. “No, because” -> “Yes, but”

    View Slide

  50. View Slide

  51. View Slide

  52. 1. Be curious
    2. Build strong systems
    3. Serve your users

    View Slide

  53. View Slide

  54. View Slide

  55. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  56. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  57. Dana Lawson

    View Slide

  58. Kelsey Hightower

    View Slide

  59. Charity Majors

    View Slide

  60. Support

    View Slide

  61. • Good troubleshooters
    • Fast learners
    • Familiar with different systems

    View Slide

  62. Bootcamp dev

    View Slide

  63. • Already know the basics
    • Mutually beneficial
    • Worst case: sympathy

    View Slide

  64. IT

    View Slide

  65. • Understand systems
    • Understand users
    • Can seem *too* easy

    View Slide

  66. Look farther

    View Slide

  67. Be curious
    Build strong systems
    Serve your users

    View Slide

  68. Tinkerer

    View Slide

  69. View Slide

  70. View Slide

  71. View Slide

  72. Organized

    View Slide

  73. r u
    ok?

    View Slide

  74. View Slide

  75. Service-oriented

    View Slide

  76. View Slide

  77. “Force push to master!”

    View Slide

  78. View Slide

  79. View Slide

  80. Carol

    View Slide

  81. Nuala

    View Slide

  82. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  83. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  84. View Slide

  85. • One to One
    • One to Many
    • Many to Many

    View Slide

  86. Apprentice

    View Slide

  87. Mentee

    View Slide

  88. Intern

    View Slide

  89. Give a talk

    View Slide

  90. View Slide

  91. Write docs!

    View Slide

  92. Ops School
    www.opsschool.org

    View Slide

  93. View Slide

  94. Share them

    View Slide

  95. View Slide

  96. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  97. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  98. Tools Culture

    View Slide

  99. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  100. Support
    IT
    Bootcamp dev

    View Slide

  101. Tinkerer
    Organized
    Service-oriented

    View Slide

  102. Options
    1. What should we teach?
    2. Who should we teach?
    3. How should we teach?

    View Slide

  103. View Slide

  104. Ops

    View Slide

  105. Thanks!
    @alicegoldfuss

    View Slide

  106. Credits
    Font -> kreativekorp.com
    Art -> pixabay.com
    Pixels -> piskelapp.com
    Ops Engineer -> #WOCinTech Chat

    View Slide

  107. Thanks!
    @alicegoldfuss

    View Slide