I used to think the problem with junior developers was that they didn't know enough yet. Now I think the problem is they never get to be bad at something without someone finding out.
Learning to code is mostly a long list of embarrassing guesses. You think the bug is in the database, it's in the loop. You think you understand recursion, you don't, not until the third time it breaks you. That ugly, wrong-guess phase is where the actual understanding gets built. Nobody skips it. Nobody ever has.
Except now almost nothing stays unseen:
- The pull request gets reviewed before you've even decided if it's right
- The Slack thread gets a reaction before the idea is fully formed
- The pair programming session has someone watching your cursor
- The standup asks what you did yesterday, so yesterday has to sound like progress
None of these are bad alone. Code review is good. Pairing is good. Stack them all together and every wrong guess has a witness. And once a guess has a witness, it stops being a guess. It becomes a performance of confidence, because looking unsure in front of someone feels worse than being wrong alone.
So they hedge. Google before trying. Ask in the channel before attempting the fix themselves, not out of laziness, but because failing alone with no one to see the attempt was reasonable feels like a risk with no upside. If nobody sees you try and you fail, you just failed. If someone sees you try and you fail, at least they saw you try.
That's the trade most junior developers make without noticing they're making it: optimizing for looking like they know, instead of the slower thing, which is actually finding out. And you cannot find out by watching someone else find out.
I don't think this is really their fault. Most workplaces reward the appearance of competence faster than the process of building it:
- A junior who asks fewer questions looks more senior, even understanding less
- A junior who ships fast looks stronger, even copying the shape of a solution without touching the reasoning
- A junior who never looks stuck gets trusted with more, before they've earned the trust
Performing readiness and actually building it are two different skills. They don't transfer to each other.
The old way was slower and lonelier, and it worked because it was lonely. You sat with the broken thing until you weren't scared of broken things anymore. Nobody graded the four hours before the fix. Nobody needed to know about them. That's exactly why they worked.
Somewhere there's still a junior developer doing it the old way. Closing the laptop on something half broken, telling nobody, coming back tomorrow with slightly less fear than the day before. Slower than everyone else in the room. Actually building something, though.
