Impostor syndrome, minus the pep talk

You've heard "everyone feels like an impostor." That's true, and it isn't very helpful. Telling someone a feeling is common doesn't tell them what to do with it.

This post is about what I try to do with the feeling: practical moves, not reassurance. It's written by a student who still feels it, so it isn't advice from the other side of the problem.

First, separate two different things

"Impostor syndrome" gets used for two very different situations:

1. A feeling that doesn't match the evidence. You've shipped real work, but you feel like a fraud.
2. A feeling that matches a real gap. You don't know something important yet.

They need different responses. The first needs evidence and perspective. The second needs learning, and the feeling is simply accurate information. Mixing them up leads to either false reassurance or unnecessary despair.

Make it concrete

"I'm not good enough" is vague, and vague fears grow in the dark. Try translating:

Vague fears are heavy. Tasks are small and have next steps. The translation itself often shrinks the feeling.

Keep a record

When I feel behind, I look at what exists: the projects, the case studies, the changelog of what shipped. That record is evidence, not opinion.

Mind you, the record cuts both ways. It also shows my gaps clearly: no tests on CardBridge, an AI eval that's never been run, a template that's built but unpublished. That's fine. An honest record of strengths and gaps is more useful than a flattering memory.

A simple version

Keep a file called wins.md. At the end of each week, add three lines (these are example entries, use your own):

2026-W42 - Fixed the RLS recursion with a SECURITY DEFINER helper. - Wrote the plan for transition tests. - Helped a friend debug a CORS error. 

On the bad weeks, read it back.

Limit the comparison

Social feeds show other people's finished work next to your messy middle. The comparison is rigged: you're seeing their highlight reel and living your own behind-the-scenes.

I try to compare myself to last month's me. Am I able to do something now that I couldn't then? That's a fair measure, and it's the only one fully under my control.

Ask the question out loud

Most "stupid questions" are the ones everyone has. Asking early is cheaper than hiding it for months and building on a misunderstanding. A good way to ask:

• Say what you've tried.
• Say what you expected.
• Say what you got.
• Ask the narrowest question you can.

People respond well to specific questions, and writing one often reveals the answer before you press send.

Notice what you discount

A common pattern: you discount your own achievements ("anyone could've done that") and inflate other people's. Try the reverse test: if a friend described your work to you, would you be impressed? If so, you may be applying a stricter standard to yourself than to anyone else.

When "I don't belong" isn't about skill

Sometimes the feeling is about environment, not ability: being the only person from your background, city or college in a room, or lacking a network. That's a real disadvantage, and telling yourself "it's all in your head" is wrong. In those cases, finding a community (online counts) matters more than any amount of studying.

What this doesn't fix

• Real skill gaps. The feeling is a signal to learn, not a verdict on your worth.
• Burnout or deeper anxiety. If the feeling is constant and heavy, or affecting sleep and health, talk to someone you trust or a professional. A blog post can't substitute for that.

A one-week exercise

1. Write down three things you're afraid you can't do.
2. Turn each into a specific, learnable task.
3. Pick the smallest one and do it this week.
4. Add the result to your wins.md.

Scripts for asking and answering

Sometimes the hardest part is the first sentence. Steal these.

Asking for help

"I'm trying to [goal]. I expected [X] but got [Y]. I've tried [A] and [B]. Could you point me at what I'm missing?"

Asking for feedback

"Could you look at [thing] and tell me the one thing that's confusing or weak? I don't need polish, just the biggest problem."

Admitting you don't know

"I haven't worked with that yet. Here's how I'd approach learning it..."

Receiving criticism

"Thanks, that's helpful. Let me check and I'll get back to you."

All four are specific, polite and honest, and none apologises for existing.

How to talk about gaps in an interview

Having a clear view of your gaps is an advantage in interviews, not a liability.

1. Name the gap plainly. "I haven't operated a production system."
2. Show you understand why it matters. "I know incident response and monitoring are a big part of reliability."
3. Show what you've done about it. "I added health checks and a post-deploy verification routine to my own projects."
4. Show the next step. "I'm looking for a role where I can learn that from people who do it."

That structure turns "I don't know" into "here's how I learn."

A quick audit: what's feeding the feeling?

Check your inputs:

• Who am I comparing myself to? Strangers with highlight reels?
• What am I reading or watching before I code? Content that makes me feel behind?
• Am I sleeping and eating properly? Fatigue magnifies self-doubt.
• Have I told anyone how I feel? Secrets get heavier.

Changing inputs often does more than arguing with the feeling.

The "evidence file" idea

Beyond a wins.md, collect:

• screenshots of kind messages or helpful reviews,
• links to things you shipped,
• the list of problems you've solved that you once thought were impossible.

On a bad day, you want to have something to read that isn't made of memory.

What helps when the feeling is about belonging

If you're the only person in your circle doing this, the distance can feel like proof that you don't belong. A few things that can help:

• Join an online community around a tool you actually use.
• Find one person a bit ahead of you and ask a specific question.
• Find one person a bit behind you and explain something. Teaching reminds you what you know.
• Share small work. Replies are a reminder that other people exist.

A note for people who feel this strongly

If the feeling is constant, affects your sleep, appetite or relationships, or comes with hopelessness, it's more than a learning curve. Please talk to someone: a friend, family member, counsellor or doctor. That isn't weakness. It's the same logic as asking for help with a bug you can't solve alone.

Reminders worth keeping

• Competence arrives unevenly. You can be strong in one area and a beginner in another.
• Experienced people also look things up constantly.
• Comparison to people with different resources is not a fair benchmark.
• The question isn't "am I good enough?" but "what's my next step?"

How do you handle it? And has anything specific ever actually helped?

☕ Enjoyed this post? You can support my writing on Ko-fi.