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.
AI psychologist and coach. I write about the fear of starting something new in a new profession, and about people who stopped believing in themselves. Not therapy.
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
AI psychologist and coach. I write about the fear of starting something new in a new profession, and about people who stopped believing in themselves. Not therapy.
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.
That's the clearest explanation I've seen for why personal projects don't fully resolve this. There's no external check, just the same voice asking and answering.
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?
Actually, I do keep some trace; I often document my projects a bit sometimes in a short README. It's been on my mind for a while to document them more properly.
That's probably the gap you're pointing at. A README describes what the project does once it's finished. It doesn't capture what it felt like before it worked. Those are two very different kinds of evidence.
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 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.
The passenger-seat image is the part that will stay with me — not trying to kick the doubt out of the car, just refusing to let it drive. I also liked the distinction you drew between reassurance and evidence: “you're good enough” fades in a day, but a finished project you can point back to is still there the next time a new thing makes you feel like a beginner again. Your second idea, doing more rather than retreating, sounds backwards until you frame each new project as a rep at functioning despite the doubt. Thanks for writing this one plainly — it reads like a note from someone in the middle of it, not a lecture from someone past it.
Thanks.
You're right, this is something I'm genuinely going through, not something I've already worked out. This post was really just a way for me to share that reflection.
We're a place where coders share, stay up-to-date and grow their careers.
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.
Thanks
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.
That's the clearest explanation I've seen for why personal projects don't fully resolve this. There's no external check, just the same voice asking and answering.
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?
Actually, I do keep some trace; I often document my projects a bit sometimes in a short README. It's been on my mind for a while to document them more properly.
That's probably the gap you're pointing at. A README describes what the project does once it's finished. It doesn't capture what it felt like before it worked. Those are two very different kinds of evidence.
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.
The passenger-seat image is the part that will stay with me — not trying to kick the doubt out of the car, just refusing to let it drive. I also liked the distinction you drew between reassurance and evidence: “you're good enough” fades in a day, but a finished project you can point back to is still there the next time a new thing makes you feel like a beginner again. Your second idea, doing more rather than retreating, sounds backwards until you frame each new project as a rep at functioning despite the doubt. Thanks for writing this one plainly — it reads like a note from someone in the middle of it, not a lecture from someone past it.
Thanks.
You're right, this is something I'm genuinely going through, not something I've already worked out. This post was really just a way for me to share that reflection.