![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8f2046ae-5d2e-495f-b467-f7b14ccb4152.png)
I totally agree with you that systemic failures require a systemic evaluation to figure out what actually happened. Most of the jobs I’ve worked have been as an analyst of one kind or another, so I of course know that many things do not have quick answers.
So yes technically I should have added some kind of qualifier, but you seem to get that I mean that common, routine job functions or system functions pretty much always should have fairly simple explanations as to why something routine happens or does not.
So, it takes me a while to do a root cause analysis of a quarter or years worth of one kind of failure in a complex process or another, but I very rarely have to manually investigate some specific totally unknown thing in person, as the system is (or should) be designed in such a way that tbis stuff is tracked and easily analyzed.
Contrast that with: Why isn’t the report released yet?
Oh, because a data set I need access to is offline right now, or some dumbass changed the access creds without informing me prior, I emailed them a week ago, and they have not responded.
That is a simple answer.
I’ve been sitting in front of a person with very poor dental hygiene who bit into sandwich…
There was a cracking/crumbling noise and the remainder of her teeth did a combination of falling out and being stuck into the sandwich.
I managed to repress extreme repulsion, but could not repress shock.
One of the more traumatizing things I’ve ever experienced.