3 ms·
That describes a CS degree heavily biased towards practical application instead of towards theory, like mine was. We only had a couple of the things in your li
by Izkata 6y ago
That describes a CS degree heavily biased towards practical application instead of towards theory, like mine was. We only had a couple of the things in your lists.
Anything that involves the physical world went in the engineering degrees - we didn't do circuits, assembly, or programming a robot. Likewise networking I think was an elective, as might have been kernels (though I don't recall that one, and didn't take either of those myself). We did talk about kernels in our systems programming course, but the extent of practical work was things like creating our own malloc and creating a simple shell.
Web apps were in the ITM courses (Information Technology something), which was where people learned specific practical skills and most people doing CS degrees didn't touch - I took one out of curiosity and it was so absurdly low-skill-level: The first assignment was creating mockups for site, then imagine spending the next few months on just HTML and CSS implementing it.
One specific example of the theory-vs-practical-application difference between our CS degrees, we didn't do compilers, we did programming language design. Parsing theory, grammars, and after learning Scheme we used it to implement an interpreter for our own language.
- ekidd 6y agoI feel like I ought to defend the honor of my school's theoreticians. :-) Their CS program had two theory-heavy courses. In the harder of the two, the homework worked out to 10 pages/week of proofs written in LaTeX. Honors students could also take a functional programming course early on, where they usually got to write a metacircular evaluator. The same CS program also had a software engineering course that required a 5-student team to spend half a term building a group project. (Teams were picked by the professor, for that real-world feel.) This usually required a UI, which meant that we got to learn Motif or web programming or something. This has always seemed like a sensible way to organize a CS curriculum: Everyone needs to write proofs, and everyone needs to write code. Then you can throw in kernels or networking as electives.