Imposter Syndrome (for software devs)
It's easy to think you're an imposter, because you surround yourself with people learning; because you struggle; because you forget things.
When you're learning new stuff all the time, you never feel like you're reaching competency. In fact, the more you learn and realize how much there is to learn, you frame competency as something that's elusive at best.
Being competent in software boils down to:
does it work the way it was intended?
In software, there are always features that could be added or removed. There are changes in the interface and speed and utility. But that doesn't preclude you from being able to make something that works.
A hammer could be different, but can it get a nail in and out? ( mostly in )
A recipe could be different, but does it fill you up and put a smile on your face?
We don't label a pizza maker incompetent because the oven had a hot spot and blackened one of the edges a little. In the same way, you shouldn't feel like an impostor because a particular browser renders your CSS a little differently than intended.
To avoid Imposter Syndrome, maybe all I need to do is ask myself: Can I get a thing working? ( no matter how long it takes ) and Am I willing to keep at it until I do?
How do you deal with this?