I 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

I 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.