this post was submitted on 17 Oct 2025
29 points (89.2% liked)
Programming
23242 readers
224 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If AI is really so good that it will democratize writing code to implement features, then why won't it also democratize the ability to come up with the correct data model? What makes that one task so special?
Were I to conjecture as to the answer, I would say that business types seem to have a blind spot where they think that every role will be commodified except their own, which is somehow special.
These people think of programming languages as a "oh so you just translate English to code."
They assume it's easy to replace programmers if you just had a similar technology to google translate. And that AI is that technology.
some things are easier to change than others. it's easy to slop on new features, rewrite them etc. changing core models after you've built a ton on them isn't easy, even with ai. the odds it comes up with the perfect data model aren't great, but for isolated features that doesn't matter since it's easy to throw them away and rewrite
Cause programmers never had to fix legacy code or anything.
all of their examples are pre ai anyway. it's almost impossible to change a core data model thing without ai too.
all the legacy codebases I've worked in have very much been shaped by the original abstractions they decided on. as much as I wanted to change them, there wasn't really a way to do so because of the scale and backwards compatibility requirements