Leaving the Nest:
Guidelines, guardrails, and human error Laura Santamaria, Developer Advocate, @nimbinatus | #FailoverConf
Photo by Mrg Simon on Unsplash
Slide 2
@nimbinatus | #FailoverConf
Human error
Slide 3
@nimbinatus | #FailoverConf
Blame
Slide 4
@nimbinatus | #FailoverConf
It’s okay to mess up… we’re human.
Photo by Jason Yuen on Unsplash
Slide 5
@nimbinatus | #FailoverConf
Failed process and mitigation
Slide 6
@nimbinatus | #FailoverConf
Framework:
Guidelines and Guardrails
Slide 7
@nimbinatus | #FailoverConf
Guidelines Photo by Chris on Unsplash
Slide 8
@nimbinatus | #FailoverConf
Guides, processes, and shared experience
Slide 9
@nimbinatus | #FailoverConf
Photo by Miguel Alcântara on Unsplash
Slide 10
@nimbinatus | #FailoverConf
Automation, alerts, and verification
Slide 11
@nimbinatus | #FailoverConf
Effectiveness increases with earlier deployment
Photo by Joel Thorner on Unsplash
Slide 12
@nimbinatus | #FailoverConf
Failure mode
Slide 13
@nimbinatus | #FailoverConf
Rushing to respond
Slide 14
@nimbinatus | #FailoverConf
Guidelines ignored; guardrails too brittle
Slide 15
@nimbinatus | #FailoverConf
Just like a habit
Photo by Patrick Hendry on Unsplash
Slide 16
@nimbinatus | #FailoverConf
Establish them early
Slide 17
@nimbinatus | #FailoverConf
Be consistent
Slide 18
@nimbinatus | #FailoverConf
Maintain them
Slide 19
@nimbinatus | #FailoverConf
Trust your guidelines and guardrails, but remember…
Slide 20
@nimbinatus | #FailoverConf
…we are still only human. (Thanks) https://nimbinatus.com https://logdna.com
Photo by James Ting on Unsplash