Confessions of a Systems Engineer - Learning from My 20+ Years of Failure

Confessions of a Systems Engineer - Learning from My 20+ Years of Failure

USENIX via YouTube Direct link

Intro

1 of 15

1 of 15

Intro

Class Central Classrooms beta

YouTube playlists curated by Class Central.

Classroom Contents

Confessions of a Systems Engineer - Learning from My 20+ Years of Failure

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 There Are No Safe Changes
  3. 3 Minimize the Blast Radius on Changes
  4. 4 Monitor Accurately and Measure Thoroughly
  5. 5 Automate Mitigations
  6. 6 Degraded Service Modes, or An Imperfect Experience Usually Beats a Nonexistent One
  7. 7 Use Functional Gates Pre-, Post- and During Releases
  8. 8 Design to Meet SLAs and Mitigate Incidents Quickly
  9. 9 Regularly Exercise All Processes and Tools
  10. 10 Enforce Processes with Technology
  11. 11 Redirect or Drop Traffic Aggressively During Incidents
  12. 12 Production Quality Tools
  13. 13 Sanitize and Verify Inputs
  14. 14 Understand All of the Scenarios You Support
  15. 15 Transition Service Responsibilities Carefully

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.