4 ms·
“Back in my day...” when I was in my last term of CS undergrad work 25 years ago, I had already developed kernel modules (in a toy/research OS) to manage concur
by obelos 4y ago
“Back in my day...” when I was in my last term of CS undergrad work 25 years ago, I had already developed kernel modules (in a toy/research OS) to manage concurrency primitives, written several networked client and server programs and readily debug them with tcpdump, could explain the differences between the 7-layer OSI model and typical 4-layer protocol stack we actually use, could describe with examples several tiers of relational database normalization, and wrote a low-level hardware I/O kit for downloading Atari 2600 carts. This was all just stuff I'd learned and written for my class projects at my very mid-tier state university. It sounds like either the curriculum standards have changed over the years, or maybe the program was more advanced at the time than I gave it credit for?
- oska 4y agoI'd agree that the 80s and 90s were probably a peak time for widespread but still rigorous computer science tertiary education (was certainly rigorous before then but not particularly widespread). At least in Western countries. The quality and rigour of CS education started heading downhill in the 2000s.
- FlyingSnake 4y agoEveryone’s not like you Linus. /s
- obelos 4y agoHeh. I mean, I was an A student, but except for a handful of duds in the class, all of my peers produced this same kind and quantity of work. There were definitely some who were sharper than me. I did not think of myself as a particularly stand-out student in my class.