Or maybe, people are enrolling in CS programs these days because they want to learn how to program. Which is a perfectly appropriate skill to teach. The fact that schools fail to teach it is their defect.
Or maybe, people are enrolling in CS programs these days because they want to learn how to program. Which is a perfectly appropriate skill to teach. The fact that schools fail to teach it is their defect.
Of course it is not a defect to teach the subject matter of the degree.
Teaching programming is also a perfectly nice skill to teach, but it's not computer science.
You wouldn't enroll in mechanical engineering and complain they don't teach how to change oil in your car.
However, equivalently, if you do study mechanical engineering and aerodynamics, you could then go into a career in car mechanics where you can get much farther (e.g. Formula 1 car development) than if you studied only fixing cars at a trade school.
The problem with this field is that software engineering and computer science and trade-school level programming all get conflated when they are distinct but related fields. Maybe it will take many more decades of maturing before the field sorts these out properly, such as has already happened in more mature fields that have been around for centuries.
If one is not interested in things that are foundational to the context they operate in, why are they there?
That said, someone wanting to learn how to program would be best served by a community college/vocational school.
CMU, UT, and UW are the few prestigious schools that I could find that explicitly offer a Master's in Software Engineering (but no undergrad degrees, certainly).
Other than that, Georgia Tech offers an undergrad certificate (3 classes). Berkeley apparently has an online program for a Master of Molecular Science and Software Engineering, wherein you mostly take chemistry classes along with one data science course and one CS course.