this post was submitted on 22 May 2025
298 points (94.6% liked)
Programming
20294 readers
378 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
Well I'm old, so no looking for a job, I am just learning programming because i want to. But to your point, I am seeing LOTS of developers who have been laid off and finding another job is proving more challenging than ever before. It's rough out there and I feel for them.
To copy what someone else in this thread said:
Oh layoffs are definitely happening. I'm just not sure if it's caused by AI productivity gains, or if it's just the latest excuse (the pandemic, then soft layoffs of "back to office" enforcement, and now AI). Esp since the companies most talking about AI productivity gains are the same companies that benefit from AI adoption...
What I wanted to explain is just that the skills to program actually translate pretty well. At my old company, we used to say "you know someone's a staff engineer, because they only make PowerPoint presentations and diagrams, and don't actually write any code". And those skills directly translate to directing an AI to build the thing you need. The abstracted architect role will probably increase in value, as the typing value decreases.
My biggest concern is probably that AI is currently eating junior dev jobs, since what it excels at is typically the kind of work you'd give to a junior engineer. And I think that more gruntwork kinda tasks are the way that someone develops the higher level skills that are important later; you start to see the kinds of edge cases first hand, so it makes them memorable. But I feel like that might just be a transition thing; many developers these days don't know bare code down to the 1s and 0s. The abstraction might just move up another level, and people will build more things. At least, this is the optimistic view. 🤷 But I'm an optimistic guy.