14
Modern software quality, or why I think using language models for programming is a bad idea
(softwarecrisis.dev)
this post was submitted on 13 Jun 2023
14 points (93.8% liked)
Programming
17378 readers
361 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The current AI doesn't produce working software on the first try. It has to be guided into it, and still requires a decent programmer to end up with a decent product at the end.
Even if the AI got it correct the first time, the initial prompt is unlikely to be correct, for multiple reasons.
This all means that AI can merely assists decent programmers, it can't replace them. It can speed them up, even if only by taking a lot of the typing out of the equation. But it can't replace them.
AI could theoretically reduce the number of programmers in a company, but my experience has been that the company has a budget for programmers, and that's what they'll pay for. I've never cleared my to-do list at work, and I can no longer imagine it actually happening, no matter how much help the computer gives me.
I remain unconcerned about AI taking programming jobs.