There are two types of engineers: (1) Those who’ve experienced the infamous imposter syndrome and (2) those who won’t admit it. Imposter syndrome is extremely prevalent in the developer community.
Imposter syndrome robs you out of confidence and joy. People suffering from imposter syndrome often feel like they’re not good enough to do the work they’re assigned to do.
Are there cases where you feel at work that you’re not good enough? That’s imposter syndrome. Carrying this constant anxiety and dread ain’t easy.
If this all is too familiar to you— this article is just for you. Here are ways to cope with imposter syndrome and eventually beat it. Hopefully, as a result, you’ll become a more confident and happier person.
Programming is hard. Like really, really hard. There, I’ve said it.
I’m not a prodigy at coding, but I never gave up, and neither should you. Programming is humbling — there’s so much to know. Accept the fact that it’s not possible to know everything about everything when it comes to programming.
We work better in teams. The more complicated the project, the bigger the team. Accept the fact that it’s not possible for you to know everything. Trust your teammates and have a support system in place.
Why do we put so much burden on ourselves to know everything? This causes the inevitable cascade of imposter syndrome effects when we cringe at the whimsical job requirements.
What do you say when a friend asks you to build the following?
“It’s like Tinder, but for cats”
You’d probably be wise to say no to that. How come we have such a difficult time doing that?
It’s difficult to say no to a person who is excited about a project. Agreeable people tend to struggle with this more than less agreeable personalities.
Saying no wakens up intensely negative emotions—embarrassment and guilt. We have to get over that and move on. We can’t work on every project.
Knowing when to say ‘no’ is a skill. Like with all skills, it’s trainable and you’ll become better at it.
You should always keep your ears open and be open to new ideas. Just learn to say no when you feel the time is not right or you’re already working on something.
As a developer, we’re students for life, and we shouldn’t forget that.
A decision-making framework: Here’s how I decide between a ‘no’ and a ‘yes’
Here are a couple of questions that should reveal how you feel about a project and whether you’re tilting more toward a ‘no’ or a ‘yes.’
Without lying to myself — Can I honestly commit to this project full-time for at least six months?
What happens if I get bored or tired of the project? Am I able to continue and push through when things get tough?
Am I getting paid? Do the bills get paid or do I have to live on previous savings?
What happens if a co-founder leaves— Will the project die overnight? Who will be the captain if a storm approaches?
Am I excited about the future of the project? Do I dream about the project and can’t stop writing code?
I bet if you take the time and go through the questions, you’ll find some clarity as to what to do.
I’m a big advocate of consistent exercise routines. We’re not genetically born to live stationary lives.
Imagine if you could buy only one car for the rest of your life — You would take good care of that car. You would change the tires and oil and bring it to maintenance more than you normally would, right?
Well, if you agree with the above, think about this for a moment. We only get one body for the rest of our lives. Let me say that once more — one body, per life. That’s it, no refunds, no swaps, everyone has to deal with the cards they’re dealt with.
We only get one body for the rest of our lives. It would be foolish to not maintain it.
It doesn’t have to be a frenzy. Start small, but most importantly, start today. Like a well-known brand says, “Just do it.”
Take the time to take care of your body and well-being.
Remember middle school? Can you remember what your favorite sport was? Go and reignite your favorite game memories.
When I started coding, I wished someone took me under their wing and showed me the way. I’m a self-taught programmer and I had no mentors to ask for help.
Fortunately, I know English and have two programming buddies, Stackoverflow and Google.
Teaching is humbling — there’s something about it that makes you appreciate what you’ve accomplished.
If you're like me and your modus operandi tilts more industrial — I have to work every day to feel normal — teaching helps with that.
Teaching also trains your patience, a priceless skill to attain.
The next time you go to work, school, or contribute to open source— pick up someone's code, review it, and leave positive notes and ways to improve.
When it comes to reviewing code and other people's work—It’s super easy to be insensitive.
If every pull request or bug report is a friendly note saying how much the users like using your application, and they include some pointers on how to improve. Those notes would be appreciated and motivate you to work harder, wouldn’t they?
Be the mentor you wish you had.
If you enjoyed this, I also write a newsletter for developers: https://thewholesome.dev/ -- I share tips and tricks, career advice, and programming news. It's 100% free, forever.