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.
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.