I would say someone on a full CS-and-engineering track should study #2 (intro), #1 (rigorous CS/math), and finish with #3, since that's where you want to focus

I would say someone on a full CS-and-engineering track should study #2 (intro), #1 (rigorous CS/math), and finish with #3, since that's where you want to focus on the latest industry standards and trends. This is similar to my own CS university experience, but I'd like to see it broken out into much better defined areas, with different ratios of focus for different career tracks. I also think a full program should take significantly longer than a 4-year degree. Incidentally, I think #1 could easily be taught without #3 at all. I get the impression that there are quite a few academic people who tinker with interesting algorithmic work, in esoteric languages, who couldn't effectively write maintainable code for mass deployment. Not that there's anything wrong with that, it's just a different area of specialization.