[cloths]

From one point I think it's fair for Uni emphasise on CS over SE because there's "truth" inherent in CS, but for SE, which deals with building software in real life, is more complicated because real-life is complicated.

Even for the QA advice in the post "writing tests as you write the software" one can argue it's infeasible/inappropriate for my type of project and/or with the people who work on this project.

So my two cents on this is let Uni teach the students *to be aware of* all the SE principles and best practices this industry now have, like the tools in your toolbox, also let us know that whether to use them in real-life projects, need assessment of situation, cost/value balance, people etc, afterall not everybody works on dream projects.