this post was submitted on 23 Feb 2026
151 points (92.7% liked)
Programming
25758 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I agree. The article the article assumes that junior developers are tasked with doing tasks that senior devs will not (such as writing buggy boilerplate or something). That has not been the case with companies I worked at. When we hired a junior developer, we expected them to write the same code as everyone else, just that they would ask for help more often and would get more nit-picky code reviews. An AI could probably outdo a junior developer with a month or two of experience, but with a (junior) developer, the expectation is that if you take the time to explain to them why their code is wrong, they will never make the same mistake again.
I agree with you that it comes down to the state of the economy. Ten years ago, I was at a company that could not hire senior devs fast enough so we had to hire junior devs and mold them into the coders we needed.
Now I am at a company that has had a hiring freeze for several years. All new hires we are getting are back-fill: when we have someone quit, we can request a replacement. Anyone we hire needs to be able to hit the ground running and take over the previous employees responsibilities as soon as possible.