That's interesting. The popular sentiment in programming world seem to be Unis don't tech practical stuff enough, or interviews for (junior) developers don't test their practical knowledge enough- a point I always found a bit strange.
In an engineering department (as in not CS) I'd say the bias is overwhelmingly towards the math end of the spectrum, partly because faculty largely don't even keep up with the technology. You'd have to heavily revise your course constantly (imagine teaching how to use google products...). Plus it just feels less worthwhile teaching things that will become obsolete in a few years.
Oh and by the way we need to teach them to write better too. Kids can't communicate these days. And economics. And ethics. It ends up being a very tight squeeze we can cram in maybe two courses on programming if it's a top priority.
In a way, F-35 (but also recent F-16) suffer from related issues, where the complexity of maintenance is staggering, and the tools you're given to help manage that suck too much.
I think the point might be that there might be a sweet spot somewhere between
- demanding Java code to be created by students using only Notepad and javac
and
- just teaching the latest js trends
I think it is fully possible - and a lot more motivating - to teach theoretical problems hand in hand with practical problems.