This might lead to more automatisation and not less if it works. After all we might extract everything critical to us.
We also now expect juniors to review the other ones code first.
I think this is pretty dubious. It's true that you have to do more proactive learning with an agentic workflow, but it doesn't mean you can't learn stuff. Software engineers forged in the age of AI are not learning the same things their predecessors did or thinking about code in the same way, but the more curious people will still be better at the job, which is I think how it's always been. It seems a little unclear how much "AI brain rot" will be a force unto itself that neuters even the smartest of the juniors, but I think it's still an open question.
But when I just ask to do a thing and then read the code (typical in a professional environment when there’s pressure to get shit delivered), i have not found that be an effective learning method.
When I’m learning from it I typically go out of my way to have it explain how to do things and things are the way they are. And I often leave the actual typing the code to myself, since that tends to force an active understanding that’s not required when you’re just reading.
If folks have other ideas on how to get that active understanding, I’d love to hear them. Because telling people they should type code seems like it’s going the way of telling people to write cursive.
About AI: Unless there's another breakthrough, AI is not getting significantly better. A junior with 2 years of proper training easily surpasses AI in judgment and arch design skills, etc. - and you will need seasoned engineers to make the calls and shepherd AI even. Where will those people come from if nobody is investing in juniors?
Now a junior takes my spec, drops it into Claude, and submits a PR a few minutes later. So I'm back to being the bottleneck -- there's constant pressure to provide specs and review code, and ultimately that process is just me having an indirect conversation with Claude (em dash is mine).
The junior is probably providing negative value, since it would be more efficient for me just to talk to Claude, and they're not learning anything, because it's really hard to learn anything by skimming code that's being pooped out by Claude.
I'm not sure what the solution to this is, I still think we need to train junior engineers. I think my best advice to juniors right now is stop using Claude so much. Use it to plan and answer questions, but you should still be writing code even it's slower. Because that's the only way they're going to learn enough to effectively guide AI and review output and get past being a net negative.