It's Worse Than You Think

With everything going on and a lot of things happening at once, I'm going to start a blog to put my thoughts down 'on paper'. We live in interesting times, and it seems a lot of people are working in concert to get what they want, regardless of the outcome for others. 

This blog is meant as more of a journal for me, to record and read back over time. My degree in Anthropology gives me a bit more insight about what's going on now. My studies of different cultures and civilizations, both past and present, I believe gives me a unique perspectives of the path we're standing on as well as what lays in wait for us down the road.

And as I get older - and hopefully wiser - I'll want to look back and see the journey with a bit more clarity. The road is getting dark, the eyes are shining off the path. 

Stay on the path.

Don't get eaten by the things in the dark.

Comments

Post a Comment

Popular posts from this blog

What is a Chaos Coordinator?

Chaos Coordinator, definition from Urban Dictionary (urbandictionary.com) -   Someone who does precision guesswork based on unreliable data provided by those of questionable knowledge Miracle worker who keeps the group going by leading, organizing, planning, and delivering with a smile fueled by passion and caffeine. Expert problem solver Expert at juggling insane amounts of activities at any given moment See also wizard, magician, miracle worker Chaos Coordinators do the following -  Use a logical, science-based, technique Organize a tidal wave of information Evaluate the day-to-day situation Learn what can be done to improve
Read more

What is Chaos Engineering?

  Chaos Engineering, definition from Wikipedia (wikipedia.org) - Chaos engineering is the discipline of experimenting on a system in order to build confidence in the system's capability to withstand turbulent conditions in production. Building Resilience with Chaos Engineering - 1. Steady state Normal Standard Regular Usual 2. Hypothesis Premise Theory  What if? Speculation Provisional Conjecture 3. Design and Experiment Testing the theory for resiliency Running through the scenario Testing recoverability Testing how the issue affects day to day life 4. Verify and Learn Analyze results Verify the hypothesis Look to see what happened What went wrong What went right Learn the vulnerabilities 5. Fix and/or Update Take action Patch Modify Improve Resolve issue 6. Repeat Re-run through the steps to find the and fix more issues
Read more

Finding the Root Cause of a Problem

  In order to determine if something is wrong it is best to know how the system is supposed to work. In the computer business this is spelled out in a Requirements Document. The document goes into great detail on functionality, how it's supposed to work, who's supposed to use it, and what task it is made to accomplish.  A good Chaos Engineer will read the document and write up a list of tests, to make sure it works as designed. But the Engineer doesn't stop there. They also write up tests for compatibility, stress, negative, and errors. The Engineer thinks up ways to exercise the system in ways that it will break. If the system does indeed break, the issue can then be reported and fixed before the product is shipped out to the customer.  In fact, it's much cheaper to fix the problem before it gets to the customer than after. Yay Chaos Engineers! If there is a problem, then it's good to look at the symptoms and look for a main cause. Better to find the cause and fix ...
Read more