I burned out in my second year as a developer. Not from the hours. Not from the deadlines. Not from the on-call rotations or the weekend deploys.
I burned out because I was performing.
Every day, I walked into the office and pretended I understood more than I did. I nodded along in architecture discussions I couldn't follow. I said "yeah, makes sense" in code reviews when I had no idea what the reviewer meant. I stayed late not because I had more work, but because leaving on time felt like it would expose that I wasn't keeping up.
That act is exhausting. Way more exhausting than the actual work.
The performance tax
Here's what I mean by performing: it's the mental overhead of constantly monitoring how you appear to others instead of focusing on the work in front of you.
You're in a meeting, and instead of listening to what's being discussed, you're calculating whether you should ask a question or if it'll make you look dumb. You get a code review comment and instead of reading it for what it says, you're trying to figure out if the reviewer thinks you're bad at your job. You get assigned a task you've never done before and instead of saying "I'll need to research this," you say "sure, no problem" and then quietly panic.
All of that takes energy. A lot of it. And it's invisible — there's no ticket for it, no sprint point, no standup update. You just slowly drain.
Why this hits juniors harder
When you're new, everything is uncertain. You don't know the codebase. You don't know the team norms. You don't know what "good" looks like at this company. So you fill in the gaps with anxiety. You assume the worst interpretation of everything.
That ambiguity is normal. But juniors don't know it's normal. They think everyone else has it figured out and they're the only one faking it.
I've mentored enough developers now to know: almost everyone feels this way in their first year or two. The ones who burn out aren't the ones with the hardest assignments. They're the ones who never say "I don't know" out loud.
What actually helped
Two things.
First, I started admitting when I didn't understand something. In meetings. In code reviews. In Slack threads. Just plain "I'm not following this — can you explain?" I expected people to judge me. Nobody did. Most of the time, someone else in the room was confused too and was relieved that I asked.
Second, I stopped comparing my insides to other people's outsides. The senior developer who seems effortlessly competent? They spent years being exactly as confused as you are right now. You're seeing their highlight reel. You're experiencing your own behind-the-scenes footage.
That's not a fair comparison. Stop making it.
The work itself is rarely the problem
If you're a junior developer and you're feeling burnt out, take an honest look at where your energy is actually going. Is it the code? The deadlines? Or is it the constant low-grade anxiety of feeling like you're about to be found out?
Because if it's the second one, the fix isn't working less. The fix is performing less.
Say "I don't know" more. Ask the question you think is dumb. Leave on time without apologizing for it.
The work gets easier when you stop pretending it's already easy.
This is one of the patterns I see most often in junior developers. I've collected 100 of these into a free guide — real mistakes, not abstract advice. Get it here.
Top comments (0)