this post was submitted on 11 Jan 2025
59 points (71.5% liked)
Technology
60453 readers
5242 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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
They're probably gonna laugh at the absurdity of the situation because some new popular language will come along and the AI will be back to pushing out broken code. That, or laugh because the code in well used languages will include a shit ton of vulnerabilities that wouldn't be present if real devs had to double check code before pushing it out to the public.
When did it ever not push out broken code?
In this hypothetical situation?
In this hypothetical, why would we create new languages? What benefit does that have for AI-gen code?
So either we're going to improve AI-gen to the point where we rely on it, or human devs are still important in which case new languages matter. The main exception here are languages specifically designed for AI, in which case error-rate would go down.
So either AI pushes out broken code and human devs are still important, or AI doesn't push out broken code and new languages aren't valuable.
Someone still has to write the instructions. AI might not become a replacement for the engineer, but a more powerful compiler, that is still fed with code written by engineers.
Yeah, I agree that's the more likely scenario. People seem to worry way too much about AI, when it's really only going to replace junior devs, and only for short-sighted companies.
But I mean many people have already lost their job because AI automated it away.
True, and many people have lost jobs because something else automated it away, like toll booth workers, grocery clerks, and telephone switchers, and computers (i.e. people who would compute things by hand).
Jobs disappearing because technology advances is natural. It sucks for those impacted, but it's natural, and IMO it's only a problem of new jobs aren't created fast enough, or whole industries disappear. Fighting to keep jobs in spite of automation runs the risk of having an entire industry disappear, such as if dock workers win the fight to prevent automation on the docks, they'll just all lose their jobs at the same time once automation can replace them all at once.
The better plan is to adjust and adapt as technology changes. If you're entering CS or a recent grad, make sure you understand concepts and focus less on syntax. If you're a mid level, learn to incorporate AI into your workflow to improve productivity. If you're a senior, work toward becoming an architect and understand how to mitigate risks with poor quality code.
Fighting AI will at best delay things.
I think both can happen at the same time. There's a lot of fkn nerds out there. (I'm a software developer myself)