Personally, I a have come to the conclusion that making business apps is no longer a STEM education required profession. If your goal is to make web apps then you will be a prompter, and the the College of Business (or College of Vibecoding, or whatever) is where the education will be. And it will be finding information for the clanker. No math, no calculus, no programming.
Computer Science will still exist. It will be 95% smaller. And the 'software engineering stuff' like requirements and actual testing and design will be explained in a couple of slides in a single lecture.
In academia, almost all AI use is wrong. Thinking, understanding, expressing yourself. The AI does not help those skills at all. The work product you create has no value; rather it is what you had to learn to make the work product. (focus on undergraduate work here, there is some nuance in research).
We have to stop focusing on the work product, and move to the journey.
The thing is... you still need to know the fundamentals if you're a clanker operator, or you end up with a barely maintainable soup of slop, badly architected, with insane amounts of code repetition and probably a boatload of security and serious performance issues that you'd know about if you'd ever been inside SQL101 or whatever "database architecture" is called in the US.
problem is, i have not reconciled my vision of the future with these edge conditions..
unfortunately, there is a big gap between reality, AI fanboys, management, societal expectations. all of those stakeholders have wildly different views of what we have today and what we can expect tomorrow.
it is a gold rush.
The worst problem with AI generated databases is the people making them have never even thought of the concept of indexes existing, or normalization of data. So they'll NIH invent their own homemade caches or automate repetitive updating of non-normalized data. Or the concept of an "atomic transaction" is utterly unknown to them. They're just lost in the woods.
For example, if you create a DB table without an index and the app eventually runs slow, non-technical people will just ask their coding agent to make it faster and the agent will add an index.
Anything that you can do without needing to physically touch the hardware, an agent will be able to do as well. Even for niche bugs that require deep technical knowledge, all it takes is one other engineer to encode their knowledge in a skill and then your knowledge is irrelevant.
I'm really happy with the education I received in uni. As part of my bachelor's I had to wrestle threads in C and C++, got O(N^2) code rejected for O(N*logN) problems, I got to write client-server apps in Java, do (graded) exercises in Prolog and Common Lisp, build web apps in PHP, configure Cisco IOS devices from scratch, draw diagrams of CMOS gates on paper, write Bash scripts handling newlines in file names, program robots in Python, write Lambda calculus expressions by hand, write XSD schemas, recognize a context-sensitive grammar, ...
I benefit from that a lot and I regularly notice that I'm using something or building upon something I remember from uni. It always seems weird to me when people say that you don't need any of that on the actual job. So what else do you need? Clicking through GitLab or Jira, remembering the 3 git commands you usually use and being comfortable in a particular IDE? You can learn all that on a rainy weekend, I'd be seriously pissed off if I'd spent my time in uni doing that.
These people tend to lack abstract thinking, and wish they had just been given a React bootcamp. They don't see it as learning networking, algorithms, files, critical thinking, software engineering, etc. They lament that they were not given specific training on specific technologies, that they then use at work.
Whats the actual job? Significant levels of underemployment has always been an issue and AI seems to be accelerating it, especially for the new players.
Some people have a natural curiosity and drive to explore and will go through great lengths to figure something out with whatever tools there are. Universities are where these people hone their skills. At least on paper. Some universities aren't actually that good at that and are glorified learning factories that prioritize churning out skilled workers rather than good researchers.
> College education for software developers has never been particularly good
Several people that laid the foundations of computer science are still alive (e.g. Donald Knuth). This field is very young. When I studied computer science, the department was staffed by people that mostly had mathematics degrees. Because there was no computer science department until about ten years before I started in 1994. How do you think math education worked a few centuries ago? LLMs literally went from being completely and utterly a science fiction topic for most of my life to science fact over the course of my professional career. I'm only 52. I still have a few decades left in my career.
There is no university program that can prepare you for that amount of rapid change. Other than to give you the mental tools to learn and adapt.
As an introductory step I would expect so. A quality professor will understand that learning is a layered process and that would be a reasonable way to have students develop the high level intuition before proceeding into the deeper layers of understanding.