> So I doubt there's any market for teaching these basics... While working through the idea, the most challenging aspect for me has been how to describe the va

> So I doubt there's any market for teaching these basics... While working through the idea, the most challenging aspect for me has been how to describe the value of it, even though I know what the value of it is. I think there are parallels, like no longer knowing what is going on under the hood of your car, which has its own anxieties. Paradoxically I think it is non-programmers who are more interested in the kind of "history lessons" of it -- like, how did we end up here, 10,000 feet view stuff. And perhaps just a small amount of that would stop people being bamboozled by copy-and-paste nonsense in proposals, quotes, project plans etc. It strikes me as interesting to think about, that if you were to go back in time and ask someone twenty years ago if they knew much about the web, those people, who might be from diverse non-technical fields, might be able to tell you quite a lot they'd gleaned about how it actually works. Because the books on the web then taught you how it worked. Surprising people used to know about domain names and FTP servers. But nowadays, the knowledge is much higher-level, and in a way that leads people into believing things only have complex dependencies, like React or serverless designs or Cloudflare. It's like the web needs its own Raspberry Pi movement.