4 ms·
I find that the list and ordering of topics is... unusual: https://csunplugged.org/en/topics/ https://csunplugged.org/en/topics/ It starts off with binary num
by userbinator 8y ago
I find that the list and ordering of topics is... unusual:
https://csunplugged.org/en/topics/ https://csunplugged.org/en/topics/
It starts off with binary numbers (and actually more on the idea of representation and interpretation of data), which is a perfectly good place to start; but why is ECC, of all things, the next topic? Then comes "Kidbots", which is an overview of programming in general, followed by searching algorithms (fair enough), but sorting networks feels like another big jump in topic.
One thing I've noticed in a lot of CS curriculum plans is this "detached binary" phenomenon and the effects thereof; like I said, it's an excellent place to start, with data representation and all the elegant yet immensely powerful implications of it. However, like the sequence here, the next topic is often only vaguely related or something completely different. To use a car analogy, it would be like spending the first lesson of a mechanic's course on the chemical properties of petrol with a brief mention that it's used in engines, and the second on suspension alignment. There's a lack of a coherent "story" that keeps the students focused and understanding "what's next".
The effect of teaching "detached binary" is that you get people who can count perfectly well in it, and will tell you they "know" binary, yet can't figure out e.g. why random 4294967295s (or 542393671s[1]) are appearing in their program's output.
IMHO the next step after learning about binary and data representation is how to actually compute with it. Logic gates, adders, latches, flops, sequential circuits, etc. The observation that one can build counters, automated adding machines, and then automated any operation machines (using data itself as instructions) quickly leads to the development of actual computers and what programming one actually means.
It is unfortunate that this code<>data duality is for many developers only ever encountered in discussions about security vulnerabilities, but it is probably one of the most important and powerful features (not bugs) of digital computing machines, alongside the generic digital representation and interpretation of data. In my experience, misunderstanding of these two concepts are a large source of bugs and confusion among both beginning CS students and long-time HLL developers (Asm'ers are, not surprisingly, far more comfortable with those concepts.)
[1] https://news.ycombinator.com/item?id=13132688 https://news.ycombinator.com/item?id=13132688 (I urge you to think about this puzzle a bit first ;)
- Karrot_Kream 8y agoIt's really hard to come up with this "story" for CS because different folks will have different needs. If you're going into hardware/embedded systems/firmware then ECC makes total sense. If you're going into academia, then maybe it's time to introduce the fields/groups portions of number coding. If you're going into high-level (web) software, then maybe it doesn't make sense. CS has so many different routes that there isn't one "story" that appeals to everyone.