April 2026 · GoCodeLab · Dev Mindset

When It Goes Well, "It Wasn't Really Me"

A five-star review lands on your app, and the first thing that crosses your mind reading it is "this person seems to have gotten the wrong idea." If that's familiar, this article starts from that single line.

That fast little dip in your chest a half-second before being congratulated. The screenshot you took to brag to a friend and never actually sent. The vague fear that "the next version will give me away." It isn't only you. It's me too. And this isn't humility. It got named precisely in 1978.

The Name: Impostor Phenomenon

In 1978, two clinical psychologists, Pauline Clance and Suzanne Imes, published a short paper. The Impostor Phenomenon in High Achieving Women. It summarized what 150 patients seen over five years had in common. People with degrees, recognized by their peers, objectively successful. Yet they all believed one thing. I am a fraud. Someday I will be exposed.

The most interesting part of the paper is the wiring inside their heads. When something good happens, it gets processed one of two ways. Luck, or good timing. When something bad happens? My fault. My lack of ability. In short, success is attributed externally and failure is attributed internally. Most people do the opposite. The ordinary self-protection circuit takes credit for success and blames luck for failure. People with impostor phenomenon have that wiring installed backwards.

Let's leave the academic terms there. What matters more is how this circuit runs in real life. A five-star review comes in. The circuit fires. "They must have misunderstood my app." "Their bar is probably low." "They'll be disappointed by the next version." You aren't receiving the praise — you're defending yourself from the praise. The compliment registers as a threat. That's the core symptom of impostor phenomenon.

Why It's Worse for Indie Devs

The circuit was bearable when I had a job. The reason is simple. External validation arrived automatically. An LGTM landed on the PR. Quarterly reviews happened. A coworker asked in Slack, "how did you write this?" Those signals kept calibrating the harsh internal yardstick. Pushing it up when it was too low. Pulling it down when it was too high.

Solo dev has none of that. You're the code reviewer, the evaluator, the design decision-maker. There's exactly one external signal: users. And the user signal is asymmetric. Happy users are silent. Unhappy users leave one star. Your inbox is permanently full of "why doesn't this work?" tickets. The silence of the people who use it just fine doesn't show up.

Here's the decisive piece. Without external signals, self-evaluation always tilts in one direction. Measure yourself with the single yardstick inside your own head, and that yardstick gets harsher with time. The indie dev's yardstick almost always tilts the same way. The good parts you built become "the bare minimum," and the weak parts become "fatal flaws." That's why a five-star review still gets processed as "luck."

On top of that, your comparison group isn't yourself. Every day you see someone's launch on Twitter. You see someone's MRR graph on Indie Hackers. You compare their results against your process. Your internal yardstick gets one notch harsher every day. No external validation, but external pressure every single day. There is no better breeding ground for impostor phenomenon than this.

Honestly, My Own Case

One time good feedback came in back to back. Three five-star reviews in a single week. One said "I've been waiting for an app like this." Another said "I use it every day." Objectively good signals.

That night I didn't sleep well. Lying there staring at the ceiling, a sentence kept auto-playing in my head. "The next version is going to give me away." I hadn't written a single new line of code, but the app that had been fine yesterday suddenly felt deficient. The next morning I started rewriting the part that worked. The screen the user said they liked — I started tearing it down.

Looking back now, it was insane. I was tearing down the part the user liked because I couldn't agree with their compliment. My head couldn't accept the praise. If I accepted it, the fall would be too big the next time praise didn't come in. So I pre-fell. I argued back at the compliment to protect myself.

This is the most expensive part of impostor phenomenon. Arguing with praise breaks the part you built best. The screen the user liked got rebuilt and, two months later, came back to where it had started. Two months gone. Those two months were the cost impostor phenomenon paid to defend my ego. Zero dollars to the user, two months from me.

To be more honest, I'm embarrassed at how much one small piece of feedback can rattle me for days. I didn't realize indie dev was a job that wobbles this hard at a single outside word. It got a little better once I learned the wobble isn't only mine. That's what the next section is about.

Real Frauds Don't Doubt Themselves

Here's a paradoxical comfort. In 1998 Paulhus and colleagues released a paper called Impostor Phenomenon and Self-Verification. A study tracking the behavior of people with impostor phenomenon. The result was strange. People scoring high on impostor phenomenon actually performed above average. The stronger the self-doubt, the more preparation, the more attention to detail, the better the outcome. And the key finding is this. These people lower their own ability ratings to maintain self-consistency. When praise comes in, they negate it. They have to negate it because that's the only way it stays consistent with the version of themselves they already hold.

Flip it around. An actual fraud has no self-consistency to maintain. An actual fraud knows they are a fraud. So when praise comes in, they just take it. No doubt, no weight. People who doubt are doubting because they are truly trying to be accountable for the work. People with no accountability have no doubt either.

If you felt "this person misunderstood" in front of a five-star review, that means you were trying to be accountable to that review. What if they're disappointed next time? How do I keep their expectations alive? The doubt came in because you took the weight. People who don't take the weight don't doubt. They just screenshot the five stars, brag, done. They might look happier than you, but they don't build a better app than you. They have no accountability behind the work.

This is what makes paradoxical comfort the right phrase. The fact that you doubt is itself a signal you're taking the work seriously. When you feel like a fraud, what it actually means is that you're a person who can be accountable for the work. The two propositions are two shadows cast by the same circuit. No accountability, no doubt. No doubt, no growth.

The Doubt Itself Is the Signal That You're Growing

One last thing. Fully escaping impostor phenomenon isn't the goal. That isn't on the table. Clance & Imes wrote as much, and forty years of follow-up research lands on the same conclusion. Impostor phenomenon is less something to cure and more something to live with. A person who drives doubt to zero drives growth to zero too.

What you have to do isn't to eliminate the doubt — it's to reinterpret the doubt. When the sentence "this isn't really my skill" comes in, translate it to "I'm being accountable right now." The two sentences are two outputs of the same circuit. You only choose which output you listen to.

When a five-star review comes in, the best way to receive it is to receive it. Don't argue. Don't analyze. Don't worry about the next version. Just take the single fact that, in that moment, that person liked your app, exactly as it is. They might move on to another app next week. The moment wasn't fake. The fact that you made that moment isn't fake either. That's also part of your skill.

If you're feeling "this isn't really my skill," you're growing right now. Only people who are growing see their own shadow. People who have stopped don't see their shadow. Keep that doubt next to you like a friend — just don't let that friend take the steering wheel. That's how an indie dev lives with impostor phenomenon.

The five-star review you got today. Screenshot it and send it to a friend. Drop the "it was luck" part. Just write "thanks." That one line cuts a single notch in the circuit. The circuit doesn't get cut all at once. It gets cut one notch at a time. And that one notch is what builds the next version.

This article reflects information as of April 2026. The cited studies don't change with time, but my interpretation of them might shift with better data.