> Make Technology Relatable and Accessible I've considered drawing up a directed acyclic graph of fault propagation in Linux. E.g., an incorrect WPA key cause

> Make Technology Relatable and Accessible I've considered drawing up a directed acyclic graph of fault propagation in Linux. E.g., an incorrect WPA key causes WiFi to be misconfigured causes the physical network layer to be unavailable causes ... big tangled DAG ... causes the web to be inaccessible causes Facebook to fail. This might be stored as a bunch of files in /usr/consequences. Software packages would come with extra files to model their usual failure modes. The error message in the web browser would refer you to the "web inacessible" node in the DAG. You would input that into a program that automatically tested for faults and walked back though the causal links to find the mistyped WPA key. The leaf node for a simple fault like that would suggest ways to fix it (keys are printed on modems, take care with O and 0, etc.) and would link to the relevant man pages. I think that a tool like this would encourage people to start learning about software. At least it would show them which small part of the big system they needed to learn right now.