282
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jan 2024
282 points (94.3% liked)
Technology
59066 readers
4390 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 1 year ago
MODERATORS
I believe it will take at least 15-20 years before the majority of engineers can be replaced. I do agree it will happen eventually. But my point wasn't about what will happen in the future. It was about whether engineers are losing their jobs due to AI at the present moment, as the article claims.
Yeah 15-20 feels right. But I'm talking about the bottom up. When AI replaces people, it'll start with the junior roles doing grunt work. I would not be surprised if entry level engineering positions are currently beginning to be displaced, or at minimum new openings evaporating.
I disagree. There are tons of software improvements that reduce the amount of grunt / unnecessary work devs do all the time, and I never hear or see anything about layoffs due to those.
Update from using Python / JS / C / Java to using Rust? You're going to be way more productive long term because you're not nonstop debugging shitty runtime issues and ancient legacy XML based configurations nobody knows about. Does that mean we lay people off since we're way more efficient now? No.