So the germ of a good idea in the article is that there's a distinction between Computer Science and the techniques used in the actual production of software (c

So the germ of a good idea in the article is that there's a distinction between Computer Science and the techniques used in the actual production of software (call it Software Engineering, but obviously that's an overused term). I think you can make a very solid argument that universities would do well to offer a Software Engineering track alongside CS, one that focuses less on formal mathematical analyses of algorithms and reticulating splines, and more on practical concerns of software teams -- different approaches to the SDLC, ways to work in a team, how to evolve existing code without breaking things. But the argument he actually makes -- that universities should be teaching "iPhone or Android development" and spend multiple semesters on that... yeah, no. If you want a trade school that's narrowly focused on teaching people a job skill that's in demand this very second, I'd argue you're misguided, but whatever; either way, it's not what universities do and shouldn't be. The point of a university is to teach you things that won't be worthless a few years after you graduate.