1,268 karma · joined July 22, 2015
Aviation operates on a Swiss cheese model; the idea is that you want many many layers of safety (slices of cheese). Inevitably, every layer will have some holes, but with enough layers, you should still be safe; there won't be a hole that goes all the way through. In this case, they basically got down to their very last slice of cheese; it was just luck that the last layer held.
I love that IT is a field where there's no required formal education track and you can succeed with any learning path, but we definitely need some better way to make sure new devs are learning about some of these gotchas.
I have to assume that there exists some language where that relationship is described in one word, but it hurts my English-oriented brain.
They certainly don't make hyperspecific claims like "this YouTuber traveled to Israel and changed his mind about the war there, as documented in a video he posted on August 18".
Granted, this is also a problem with the obscure moth species articles. I think the moth species articles survive because no one really cares enough to start the crusade against them. When we used to have every Pokemon, it was a common line in deletion discussions to say "well if every Pokemon has an article, why can't <my obscure topic> have one too?" -- I think some people eventually got fed up and decided it was worth putting in the work of figuring out what the notability standards should be. What I've learned from a long time of editing on Wikipedia is that often, things are the way they are not because it's the best way, but because the project has a lot of inertia -- it's a lot of work to make a big change happen.
The concept you long for sounds a little bit like Wikidata. It's much less in-depth than Wikipedia, and just describes its subjects as structured data instead of with prose, but the notability bar on Wikidata is much much lower. Every Pokemon, every scientific article, every book, every village, every athlete, etc is generally in scope.