Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The ultimate guide to complicated systems - December 2019 Talk

The ultimate guide to complicated systems - December 2019 Talk

Key practices for building and maintaining complicated systems

Jennifer Davis

December 12, 2019
Tweet

More Decks by Jennifer Davis

Other Decks in Technology

Transcript

  1. She/her

    View Slide

  2. SRE… DevOps…
    Agile... Lean…
    Velocity…
    Serverless,
    Kubernetes,
    Cloud Native…

    View Slide

  3. SRE… DevOps…
    Agile... Lean…
    Velocity…
    Serverless,
    Kubernetes,
    Cloud Native…
    Value Stream
    Mapping,
    Wardley Maps
    Continuous
    Security,
    Continuous
    Testing..

    View Slide

  4. SRE… DevOps…
    Agile... Lean…
    Velocity…
    Serverless,
    Kubernetes,
    Cloud Native…
    Value Stream
    Mapping,
    Wardley Maps
    Continuous
    Security,
    Continuous
    Testing..
    Observability,
    NoOps,
    NewOps

    View Slide

  5. What’s Next?
    Image by watabou on one-page-dungeon

    View Slide

  6. Snowflakes are cool.

    View Slide

  7. Define Value.
    Photo by Riccardo Annandale on Unsplash

    View Slide

  8. Bit Learning by Ashley McNamara is licensed under CC BY-NC-SA 4.0

    View Slide

  9. Photo by Ales Krivec on Unsplash

    View Slide

  10. Photo by Tyler Casey on Unsplash

    View Slide

  11. View Slide

  12. Issue and pull request templates and config.yml
    Issue and pull request templates customize and standardize
    the information you'd like contributors to include when they
    open issues and pull requests in your repository. For more
    information, see "About issue and pull request templates."
    SECURITY.md
    A SECURITY file gives instructions for how to responsibly
    report a security vulnerability in your project. For more
    information, see "Adding a security policy to your
    repository."
    SUPPORT.md
    A SUPPORT file lets people know about ways to get help with
    your project. For more information, see "Adding support
    resources to your project."

    View Slide

  13. View Slide

  14. Understanding isn’t
    guaranteed.
    Photo by Sarah Norris on Unsplash

    View Slide

  15. Baby Facepalm by Ashley McNamara is licensed under CC BY-NC-SA 4.0

    View Slide

  16. View Slide

  17. Minimum Viable Response Plan: jhand.co/CreateResponsePlan

    View Slide

  18. View Slide

  19. Managed chaos
    builds resilience.
    Photo by Tim Cooper on Unsplash

    View Slide

  20. Weekly Oncall Review
    Photo by Tim Cooper on Unsplash

    View Slide

  21. Documentation will be wrong.
    Photo by Daniel Koponyas on Unsplash

    View Slide

  22. You will make mistakes.
    Photo by Jamie Street on Unsplash

    View Slide

  23. Blameless Culture
    Photo by Rebrand Cities from Pexels

    View Slide

  24. Trust

    View Slide

  25. Identify Quality Measures.
    Photo by Jakub Kapusnak on Unsplash

    View Slide




  26. View Slide

  27. Clean up continuously.
    Photo by The Honest Company on Unsplash

    View Slide

  28. Change is Inevitable.
    Photo by VanveenJF on Unsplash

    View Slide

  29. Bit by Ashley McNamara is licensed under CC BY-NC-SA 4.0

    View Slide

  30. Recognize Trauma.
    Photo by Rene Asmussen from Pexels

    View Slide

  31. Find Balance.
    Photo by Danne from Pexels

    View Slide

  32. You don’t
    have to do
    it alone.
    Bit Community by Ashley McNamara is licensed under CC BY-NC-SA 4.0

    View Slide

  33. Keep Learning.
    Bit by Ashley McNamara is licensed under CC BY-NC-SA 4.0
    • Blog at dev.to
    • Community meetups
    • Open Source Projects
    • Linda, and O’Reilly Safari
    • Online Training
    • Microsoft Doc Learn modules
    • Test Automation University

    View Slide

  34. View Slide

  35. View Slide