DEV Community

Cover image for How to deal with Imposter Syndrome
Heru Hartanto
Heru Hartanto

Posted on

How to deal with Imposter Syndrome

What is Imposter Syndrome

As developer did you ever feel that you're not good at your job, you feel that other developer is better than you, their code is look cleaner and more efficient, you feel incompetent and useless.

Guest what you're not alone, as many as 58% of tech worker feel imposter syndrome.

In simple term imposter syndrome is feeling of self doubt event though you already have excellent skill and achievement, it will make you suffer with insecurity, demotivated and anxiety.

This list is an indicator that you have imposter syndrome

  • Fear of getting exposed as a fraud if`` your colleague expose your knowledge gap with them
  • Feel that you're not fit with your job
  • Fall behind your colleague's performance
  • Only doing "comfortable" task

How to deal with it

1. Realize if you have Imposter Syndrome

It's is a good sign that you recognize if you have Imposter syndrome, many developers don't realize if they have it and just ignore it.

2. Moving out from your comfort zone

Nobody in tech industry is expert at everything because technology always moving, the best developer is the one who able to keep learning and adapting to industry needs.

You must learn to deal with situation that make you feel uncomfortable such as doing task that you never done before, learning new language or using another framework that you never use, with doing things that you don't know you will expand your skill and you will feel more confident with yourself.

3. Don't compare

Don't compare yourself with other colleague, this behavior will make you look down upon yourself, so whenever you achieved something in your job it's because your effort, don't look down to it and celebrate every achievement.

4. Don't quit

You need determination, persistence and discipline if you want to level up in this field, look back in your journey and you will realize that you already make big improvement, you just need to continue and see a failure, mistake and a bug as opportunity to grow instead of step back.

Cover image

Source

Top comments (0)