Chaos engineering bottom up.

Chaos is the most dangerous thing in this world. It is all around us all the time. Without control, chaos will kill you. You may recognise this quote from Witcher.

I won't discuss how to recognise demons and what sword works best on dragons. Instead I'm going to discuss chaos engineering. While it might be a surprise, Witcher's chaos definition has a lot in common with software development. Chaos is definitely something we shall understand, appreciate and... play with.

Wait did you just say play? Like play with fire? It doesn't sound like a good idea. While counter intuitive, playing with chaos is the only thing that's gonna help your team improve and move forward. Noticed "team" in the last statement?

Instead of looking at chaos engineering from individual perspective, I'm gonna look at it as a team practice. Discuss available plays. Share lessons from our try outs and how we've been continuously improving our plays to optimise for different objectives. Not sure how Chaos Engineering fits into your role and responsibilities as QA?

I believe you can become great in facilitating and brainstorming experiments. QA are recognised for their broad view of the product and system behind it. Their superpower is finding scenarios worth exploring and learning from the results on the flight. All those skills are very important when running Chaos Engineering experiments.