@futurebird I’m not sure I have a list. Coming up with a good taxonomy for computer science is something I’ve struggled with. At a minimum, I would like people to understand how to decompose problems into smaller ones (induction can help here as a concept, but it!s often taught as an ends to itself) and how to think about unambiguously specifying things so that they can be automated. These skills are essential to programming but are also generally useful. I’d also like people to learn some graph theory and queueing theory, because many real-world problems (as well as bits of computer science) depend on them.
Edit: The thing I’d like to see form any such list is why the things are important. There’s a lot that we claim is computer science (including a load of things other people claim are their own discipline, such as maths, engineering, psychology, economics, or physics). I’m not so interested in what an exhaustive list of ‘things that are computer science’ looks like (I don’t really think siloing knowledge is helpful), but in a list of ‘what things are traditionally regarded as computer science but should be general knowledge’.