Lately it feels like it's possible. Freshers in their first job are now capable of taking ownership and shipping full stack features in a few weeks. The feedback loop is definitely shortened - noone appreciates the years spent "googling and looking at stackoverflow" anymore, and frankly, they shouldn't be. Experience matters now mostly at the architecture, and decision-making levels, not at implementation.
Freshers certainly can give the appearance of taking ownership and shipping full stack features in a few weeks.
The problem is that "I copied the issue on claude code and then committed the code it produced" is not actually taking ownership.
> noone appreciates the years spent "googling and looking at stackoverflow" anymore, and frankly, they shouldn't be.
Well, I do, and I hard disagree with you there. If the human does not understand what the machine is producing, then I need a different human.
I was reviewing some code done by a junior hire at my company last week, and it certainly didn't look like he was cramming 25 years into 2. It looked like he had no understanding of anything he had generated, because it was garbage. Meanwhile this week I've just reviewed the largest single PR I've ever seen, from a senior dev who disclosed it was mostly generated and cleaned up by him, and the code was perfectly fine and it was a breeze to review.
LLMs are a great tool, but more often than not it does show if the person using them knows what they're doing or not pretty clearly. Especially if it's anything larger than a trivial small change.