How do you deal with imposter syndrome?

I experience this syndrome like almost every team meeting, there are technologies that a lot of them knew but I don't know and I always felt I am the dumbest person in the room.
I can't really say any tips as I am still overcoming it but I keep myself updated and whenever I knew the topic I share my opinion what I really think about it.

For me, I've accepted the feeling will always surface from time to time. It's hard to completely avoid it. However, knowing that it's there can help push it aside quickly.

Everyone is always learning. Each of us has a unique set of experiences and those experiences form our understanding of tech, programming, and everything else in our lives. Knowing that, we all have something to offer.

The best way to combat impostor syndrome is to keep showing up. Keep learning. Continue searching for knowledge. That's what I've learned and that's what we're all doing anyway.

It's OK to stumble around in the dark to find the light switch because every new problem starts with some darkness.

Over twenty-five years in the field, I'll try to say something that most people don't get to notice and are terrified to say out loud: We all have imposter syndrome, and it's because we're all imposters. And there's your solution.

What I mean is that nobody "evolved" to hold a job or solve problems for anywhere from hundreds to billions of people. As developers, none of us was "meant" to write code, a field that quite a few living people are still old enough to remember not existing at all. And if any of us was ready for our work, it'd already be complete. So, we're all really just pretending that we're good at this and doing the best we can, and if you don't think you are...you're wrong. The functioning people, I suspect, are the people who have internalized this as a normal state of affairs, in the same way that the people who "fit in" socially are the people who accept that nobody ever really fits in.

That has the seeds of fixing the problem, because we have a support group with seven billion members sitting right here. We--primarily white and Asian guys who make up the majority of the field--need to normalize saying "I need to learn that" and, instead of being shocked that someone doesn't know something, being excited at the chance to introduce them to it. It needs to be OK to be doing a job you're learning as you go, because that's the only kind of job there is.

I think for me it was after doing some teaching. In order to teach something, I needed to make sure I knew why I was writing code in the way I was writing it; and several times, as I went over what I was about to explain in my head, I realised I didn't fully grasp why things were the way they were, and so I did some research into it so that I could explain why I was writing the code that way.

After a while of doing that, I realised that I was filling in a lot of gaps in my knowledge, I now knew not only how to do something by why I was doing it that way and not one of three other ways. I felt that did a lot to banish impostor syndrome because at least for the stuff I was doing, I now knew I had a solid understanding of it and wasn't just doing it because I saw someone else do it in a tutorial once.

Other than that, it was just time. As I progressed with my career, and could count more successes as part of it, I think slowly that built up some self-confidence that I lacked.

I have this a lot. I've started trying to track how I'm talking to myself, even outside of the moments where my stomach sinks. A lot of the time when impostor syndrome feelings are running high, I have something in the back of my head calling me names and making statements that basically say I am not able. I try to tell that voice to shut up, and I argue with it.
I think I need to do some work on why my performance at my job is such an important part of my self-esteem. Work is just work, but it feels like more than work.

I feel this like every month. I just give myself time with other things except coding. Imposter Syndrome often happen due to burnouts and seeing people better than you so I think about what I have and what the other person doesn't have. It does take time but works at least for me.

Remember that everyone has it, and a lot of them actually are impostors:

Software development is a young field, and we are alchemists (or astrologists, if you prefer) trying to figure out how the hell do I debug my 1238 microservices?

It means that nobody is really good in it, that we miss very often what's really important (what we build and its outcome, and not tab vs space vs static typing vs OOP), and, more important, that almost nothing we consider The Truth was scientifically proved. You know, science, the stuff which brought us computers at the first place.

It means that we are all imposters. We should all be humble, listen to our peers, question them, bring diversity in our companies, but never affirming that we are right because that's how it works because I know and Uncle Bob agrees.

Imposter syndrome will always creep in from time to time. I'm bad, everybody else is better. My counter-thinking: I'm not that good, and everybody as well, because we are all explorers. That's not only fine, but exciting.

This is great! Thank you for doing this. You already have a lot of content there.

Coincidentally, later this morning (noon ET) I am hosting a talk on imposter syndrome that you may be interested in called The Power of YES Against Imposter Syndrome and featuring Hiro Nishimura, founder of AWSnewbies. (note for anyone who misses the live event, the recording will be available at the same URL).

For me personally, my best coping mechanism to combat imposter syndrome is to look over old projects. You (generally) realise that even if you're still making mistakes, you can see improvements you could make to your old projects, this (to me) shows improvement and progress.