I keep waiting for it to go away.

Every new skill, every finished project, every piece of positive feedback I expect it to be the thing that finally makes me feel like I actually know what I'm doing.

It never fully does.

The gap between what I know and what I feel

On paper, things are going well. I'm building real projects. I'm writing about what I learn. People are reading, commenting, engaging. I'm gaining actual experience, not just theoretical knowledge.

And yet there's still this quiet voice that shows up every time I start something new. "What if this time it's obvious you don't actually know what you're doing?"

It doesn't matter how many times I've proven that voice wrong. It shows up again at the next challenge, as if none of the previous ones counted.

I think what surprised me most is realizing that experience doesn't automatically silence it. I used to believe imposter syndrome was something you'd eventually "graduate" from that at some invisible threshold of skill or project count, the doubt would stop.

I don't think that's true anymore.

What actually helps for me

I haven't found a way to make the feeling disappear. But I've found something that helps me function despite it.

I go back and look at what I've already built.

When I'm staring at something new and feeling like a complete beginner again, I force myself to remember a project I did before that felt exactly the same way at the start. Something that also felt confusing, overwhelming, impossible and that I finished anyway.

It doesn't erase the doubt. But it gives me evidence against it. Not abstract reassurance like "you're good enough" concrete proof: "I felt exactly this lost before, and I figured it out."

That shift from reassurance to evidence matters a lot to me. Vague encouragement doesn't really land when you're in the middle of doubting yourself. But a specific memory of a specific project you actually completed? That's harder to argue with.

The second thing: doing more, not less

The other thing that helps me is counterintuitive. When I feel like an imposter, my instinct is to retreat stick to what I already know, avoid anything that might expose the gap I'm afraid of.

But I've learned that the opposite works better.

I try to take on more projects. Explore more technologies. Deliberately put myself in situations where I don't fully know what I'm doing yet.

This sounds like it would make imposter syndrome worse. In practice, it does something different: it normalizes not knowing. If I'm constantly starting things I'm not fully prepared for, "not knowing yet" stops feeling like a personal flaw and starts feeling like a normal part of the process.

Every new project is a small rep. Not at making the feeling disappear but at functioning well despite it.

What I've stopped expecting

I've stopped expecting to reach a point where I feel fully qualified before starting something new.

I don't think that point exists. I think even people with 20 years of experience feel some version of this when they step into genuinely new territory a new domain, a new type of problem, a new level of responsibility.

The goal isn't to eliminate the doubt. It's to keep building anyway, with the doubt sitting quietly in the background instead of in the driver's seat.

If you deal with this too what actually helps you? I'm genuinely curious whether other people have found something that works, or if we're all just figuring this out project by project.

This is a more personal one than usual part of the same series where I write honestly about building, learning, and growing as a developer.

Follow along on LinkedIn