> But that's not only what SE about. It's also about taking all the various algos, data structures and design patterns in a system, and pulling them together on time, on spec and on budget.

Unfortunately, no-one has yet worked out how to do that reliably and repeatably, which is why "software engineering" isn't.

Then again, "computer science" isn't either.

If we're going to have a sensible discussion about splitting theoretical/mathematical courses from practical/applied ones, perhaps we should start by completely removing the misleading terms CS and SE from the debate.