alt Hacker NewsI think the whole teaching the history of computers is a big failure at an attempt to Segway into computer organization and architecture. Nonetheless, I get what is happening. If it’s a pure Computer programming class then the goal maybe to have them understand the “basics”…like what is the hard drive vs RAM (memory allocation) or what is a transistor (Boolean logic) and what is a punch card (mnemonics and abstractions of those mnemonics to what is now just a computer programming language).
Replies
Personally, I struggled a lot in my earlier CS/Informatics education, partly because I never felt like I understood what was actually happening/how we got here, everything was just factoids in a void. When I took a gap semester between my A.S. and B.S., I finally studied/explored a bit of the history and it put a lot finally in perspective.
> have them understand the “basics”…like what is the hard drive vs RAM (memory allocation) or what is a transistor (Boolean logic)
You must understand these things at least conceptually if you want to really understand how to write efficient programs. Maybe not at the level of how memory can electronically "remember" a 1 or a zero, or how a hard drive can magnetically do it, but at least the relative speeds e.g. register vs. cache vs. RAM vs. disk.
(Unless you're riding a motorized vehicle, the word is segue, not Segway)