this post was submitted on 13 May 2026
34 points (92.5% liked)
Asklemmy
54307 readers
720 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm frustrated with the fact that AI is replacing a lot of junior positions, and with people that use it to fully automate tasks. It does not bode well for the future of the industry.
I'm not a junior dev though, and I use AI as a tool, which is what it is, to plan changes, search for potential issues while I check something else, then review their output and so on. The premise is that I do understand our code very well, and that I know exactly what must be done when proposing changes. It helps me autocomplete while I write, check hard to find docs or write/format doc pages. I always search for actual real sources before committing anything.
It's a tool, it would be crazy to keep using a hatchet because chainsaws sometimes injure people. With proper training and knowledge a chainsaw helps you work faster.
Now, there was no LLM when I was a junior Dev so I acknowledge that my position is a bit of "f u I got mine", but we can't deny that it's a very useful tool that helps in coding
Still completely against and very frustrated with the full automation and erasure of junior positions though. It won't affect me that much personally, but the industry will hurt, individuals will suffer and that's horrible.
You're right. That is a very "fuck you got mine" position to take.
I will say I have 3 friends, all senior devs. 2 got laid off this month. It doesn't affect you until it does.
I'm not taking that position, I'm taking the position of acknowledging how badly it is being used while also taking point on how useful for Devs it is. I was acknowledging the position I am in due to my life in coding work, to give proper context.
You are in an Australian server, I didn't know that the American AI Dev erasure craze had expanded there, it definitely is affective the Spanish junior positions, but in my data engineering sector, senior positions are permanently lacking.
In any case, I'm sorry for your friends, but I'd be surprised if they don't find another job fast. Job offers in my country for senior positions have not been reduced, and given that junior positions are being reduced and seniors eventually retire, I don't see enough reduction to fill the vacuum that the lack of junior is going to create in senior fields.
Mind you, I'm not saying this to say I don't care, it's actually the opposite. I'm saying this to say that I care even though I don't think it will affect me personally in a risk my paycheck kinda way.