Theo's Corner
dev / irl / thoughts
← Back
techlife

How I handle imposter syndrome as a self-taught dev

Theo|Jun 2026|~4 min read

Imposter syndrome is the feeling that you don't actually know what you're doing, that you're going to be found out, that the people around you are the real developers and you're just someone who figured out how to fake it well enough. It's extremely common in tech. It's even more common if you're self-taught, because you don't have a degree or a bootcamp certificate to point at when the voice starts.

Where it comes from for self-taught devs

When you're self-taught, you have gaps. Everyone does — even people with CS degrees have gaps, they're just different gaps. But when you're self-taught the gaps feel more like evidence of illegitimacy than they do for people with formal credentials. You didn't cover algorithms properly. You learned frameworks before you learned fundamentals. You figured things out in the wrong order because you were learning by building rather than by curriculum. The imposter voice uses all of that.

The gaps are real. The conclusion the imposter voice draws from them — that you're not a real developer — isn't.

What actually helps

The most reliable thing for me is looking at what I've actually built. The server host I work at runs on infrastructure I manage. The panel, the APIs, the nginx configs, the Docker setup — I built and maintain all of that. It works. Real people use it. When the voice says I don't know what I'm doing, the evidence says otherwise, and I try to weight the evidence more heavily than the feeling.

Talking to other developers also helps — not to compare, but just to discover that everyone feels this way sometimes. Even people who are objectively very good at what they do describe the same feeling. It doesn't go away with more experience, it just becomes more familiar and less convincing.

The reframe that actually works

Being self-taught doesn't mean you learned less — it means you learned differently. Everything I know, I know because I needed to know it to build something real. That's not a weakness in the knowledge, it's actually a strength. I understand things because I used them, not because I passed a test on them. That understanding tends to be stickier and more practical than credential-based knowledge.

When it's useful

A small amount of imposter syndrome is actually fine. The part that says "I should understand this better" is just accurate self-assessment, and accurate self-assessment is useful. The problem is when it scales past that into "I shouldn't be doing this at all." That part isn't accurate and it isn't useful, and recognising the difference is most of the work.