Imposter Syndrome

So Imposter Syndrome basically is when you feel like you aren’t in the right place as a programmer. You feel like what you are tasked to do is too advanced for your mindset, and that others around you seem smarter and more confident in their works.

It affects developers in ways that aren’t ideal, such as a developer becoming overwhelmed with the work at hand, or even them quitting because they have too much stress with deadlines. Some may also start to produce more but less quality work to fill in a void they may feel. A majority of developers feel this way, but may not act like it because they don’t express their stress or their feeling of being overwhelmed.

According to Urie’s post, it’s actually good to get comfortable/used to being uncomfortable. There is always more to learn in the computer science field as things change every day. It would be likely impossible to “master” computer science fully, with knowledge of everything. Growth mindsets are a good thing to have if you want to improve. Instead of viewing projects as challenges, view them as opportunities to learn and expand your knowledge. Finding out how you’re doing is also a good way to get more comfortable with your job. Asking whoever your supervisor is or person you’re submitting to how you’re doing or which submissions were the most successful helps you feel accomplished. Knowing your successful submissions is a great way to keep your head up.

I’ve experienced imposter syndrome a lot throughout the years of programming. I’ve felt that what I’m doing is too advanced or what I’m familiar with seems like the bare bone programming knowledge. Before taking this class, I had no knowledge of methods just from my own ineptitude to retain information of those more advanced topics. I’m the type of person who will go back to their own programs to find out how I did something, because usually it isn’t something that I know off the top of my head.

I feel like another way to combat imposter syndrome is to actually go out and learn more than what you are taught. Say you’re in a class learning java. You’re learning methods, and down the line you learn about inheritance. Read about inheritance before you get to the topic in class so you already have some knowledge and feel more comfortable with what you’re learning.

Leave a Reply

Your email address will not be published. Required fields are marked *