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
Top comments (15)
Shipping real projects and still waiting for the fraud feeling to clock out is more common than people admit. The gap between what you know and what you feel rarely dies from one more skill. Curious whether the voice is loudest before you start, or right after something lands and people notice.
That matches what I feel too. Each finished project does add real confidence and experience.
But the feeling resurfaces specifically when I start something completely new. It's really the unfamiliar territory that triggers it. Which is probably why experience doesn't make it disappear entirely; there's always a next first time.
"There's always a next first time" is a great way to put it. Maybe the aim isn't for the feeling to disappear, but to recognise it faster: ah, this is the new territory bit again, and I've been here before. When you think back to past firsts, what got you through that first week of not knowing? If you'd ever like to talk it through properly, I run a free 30 minute call, no pressure either way.
Recognise it faster might honestly be the more realistic goal than making it disappear.
Thanks for the offer; I appreciate it. I'll keep that in mind.
Glad that one was useful. Good luck with the next "first time", whenever it shows up.
The evidence trick has a shelf life. It works on the second attempt at something familiar. It fails the moment the thing is genuinely new, because a finished project isn't proof you can do this one. It's proof you could do the last one. The doubt asks "can you do this?" and no memory answers that.
What I've seen move people faster than looking back: someone else needing something from them before they're ready. A real task from a real person beats a shelf of finished work. Being asked for something is what makes you feel in the room. A greeting doesn't.
Still keep the record. Not to prove you're capable. To prove you've been lost before and it passed.
That's a real limitation I hadn't fully named. You're right the evidence answers "I've been lost before and found my way through," not "can you do this specific thing." Those are different questions, and the doubt is asking the second one.
The point about being needed by someone real is interesting. I think that's why client work hits differently than personal projects
The judge part is the whole thing. On a personal project you're both the client and the judge, and the judge is the one who doubts. Put a real person on the other end and the judgment turns specific: they need this by Thursday. Specific is a question you can answer. "Can you do this?" isn't.
One caveat that comes with it. Some people try to end the doubt by saying yes to a client they can't actually deliver for, and they get the proof and the fear in the same week. The ones who come out steadier took something small first. A real date, stakes that wouldn't be fatal.
Anyone who could hand you a small task right now? Not a favour. Something with a date on it.
The shift from reassurance to evidence is the useful part here. A specific memory of finishing something that felt just as confusing is hard for the doubt to argue with, while "you're good enough" slides right off. It might help to write those moments down when you finish, since the memory of how lost you felt fades fast once the thing works. Do you keep any record like that, or is it all from memory?
Honestly, mostly from memory, and you're right that it fades fast. A few months after finishing something, the confusion softens and it starts feeling like it was always obvious.
That softening is exactly what makes the evidence disappear. Even one line written the week something finally works, what was confusing and what fixed it, would keep the before picture intact. Have you tried keeping anything like that, or does it feel like extra work?
Looking back at a project that felt just as lost at the start is such a good move. Your brain has a filter that only lets in what it already believes, so vague reassurance bounces right off. Concrete evidence from your own history is the kind of thing it actually has to process. And building with the doubt in the background instead of waiting for it to leave is the whole game. The feeling shows up less once you've stacked enough reps where you didn't know and figured it out anyway.
That explains exactly why vague reassurance never worked for me, even when I logically knew it was true.
That shift from reassurance to evidence really resonated with me ā "I felt exactly this lost before, and I figured it out" is a lot more useful than just telling yourself you're good enough. I also liked the counterintuitive point about doing more, not less, when the doubt shows up. Putting the doubt in the passenger seat instead of waiting for it to disappear feels like a much more honest way to keep building.
Telling yourserlf "You're good enough" never really worked for me because. There's nothing to check it against. But a specific memory of a specific project I actually finished; that's something concrete I can point back to when the doubt shows up again.