Good lord what a moronic piece of drivel. It screams "I have no idea how this product works, but I won't let that stop me from bashing it!"
A someone that easily uses a Chromecast with my wife and children, you need to shut up until you learn about what you are bashing.
High-level theories and models and UMLs and chess board Java CS projects are most definitely useful to 99.9% of tech employers. High quality employees will apply those concepts to write efficient, maintainable code regardless of the particular language being used on a project at a tech company. Once the students have learned those high-level concepts, learning how to apply them to the syntax of a particular language is the easy part, and the student will also be able to go out an learn multiple other coding languages with ease. Like the file out question you mentioned: they might not know how to do it in a 4-line script, but they will know the general algorithm behind how to do it (or at least they ought to if they've learned high-level theories). Teaching them the syntax for it in a particular scripting language is a minimal investment after they are hired.
Techology evolves, software suites come and go, but the theories will be always be applicable. Unless you want the students to become useless once a particular software suite becomes outdated, you teach the theories that will always be applicable. Tech employers that hire solely based on knowledge of a particular software suite are very short sighted and get what they deserve.
Factorials were someone's attempt to make math LOOK exciting.