1 2 3 Automate

J. Jossemar Cordero R.

Jul 18, 2022

Disclaimer

The views, thoughts, and opinions expressed in this presentation belong solely to the author, and not necessarily to the author’s employer, organization, committee or other group or individual.

Who’s that guy

  • ex-manager, now tech lead
  • 13yrs of career in tech industry
  • Involved w/ DevEx and Delivery projects
    • AKA “DevOps”

What’s going on with the title?

Some alternative titles

  • SRE oversimplified
  • 1 2 3 Magic… Well not really
  • Kelsey said it first! (Tweet)

Story time

1 2 3 Automate!

1. Identify

  • Pair with someone has done it before
  • Be part of the process (ie: Cutting a release)
  • If possible, do it yourself at least once

2. Document

  • Let other to peer review it asynchronously
  • Allows you to socialize existing bottle necks
  • At minimum draft it on a piece of paper

3. Understand

[…] if you understand what you’re doing, you can automate if you want to

Kelsey Hightower - (Tweet)

Automate!

When to automate?

Quick tips

  • Automate what constraints the whole system
  • Automate what is wasteful or “toil”
    • The Site Reliability Workbook - Chapter 6 (Free eBook)
  • Keep it simple
    • KISS principle

Questions?

Thanks!

Github › jossemarGT
Twitter › jossemarGT