Impostor Syndrome Software Engineer (smash it by 3 good practices)

Impostor Syndrome Software Engineer (smash it by 3 good practices)


Hi guys, this is Lee. Welcome back to the channel. If this is your first time here, you want
to see videos about game development and programming, consider subscribing to my channel and turn
on the bell. Then you won’t miss my next episode. In this video, I would like to talk about
developer impostor syndrome. Initially, it is not on my list. But recently youtube start feeding me a lot
of videos related to this topic. I feel a little bit offended. Is that because I start making games myself? Youtube starts worrying about me that I may
experience some difficult time at the moment. Just in case you are not familiar with impostor
syndrome. It means you may feel you are fraud or fake. You are not good enough to get a job or stay
in the company. It is widespread in the tech field; almost
58% of the tech employees suffer from impostor syndrome. In this video, I will show you how I smash
impostor syndrome. I hope you can pick up some ideas. Then you don’t need to waste your time and
suffer from this anymore. The first one is to develop our skills. There is no easy trick that helps us overcome
impostor syndrome. But if we keep growing our abilities, it will
help us to improve our self-confidence. To be specific, we need to read a lot of books
and write code every day. When I started learning C#, .net framework,
and other Microsoft technologies, I have been reading more than 100 tech books. These books cover almost all the topics about
software development, like programing language, framework, low-level tech, design pattern,
coding practice, project management, software development methodologies, etc. And I practiced coding every day. Then I found that I knew a lot of things that
the other people may not know. It helps me to have the self-confidence at
the early stage of my career. Another good practice is that we shall join
the community. You can try to answer some of the questions
the other developer raised. Just imagine if that’s the problem you have
to solve in your daily job, are you able to fix it? By answering different questions and help
other people solve the problem, I become more confident. Sometimes even I don’t know the solution directly,
but I won’t get panic anymore. Because I already got the experience to locate
the right resource and solve the problem efficiently. The next good practice is to look for challenges. Many developers would be satisfied if they
can handle the daily job. But I don’t think that’s a good idea. Because if we get too comfortable, we will
become fragile if something gets changed. E.g., the programming language may not be
used anymore. There is no future for a specific framework
or platform. I am always looking for some challenges. I am the kind of person who will get bored
quickly if the job is too easy. Because I believe the job, company, even the
business can be changed except for one thing, which is my skillset. By investing or developing my skillset, I
am not scared of losing a job, or somehow, the whole department gets sacked. Yes, I have seen this happened in my career. The other department just got sacked because
the company’s strategy changed. So don’t get too comfortable. Always look for challenges and make yourself
ready for the changes. I also found some common mistakes that people
made. The first mistake is that some developers
try to learn everything. No matter it is about the programming language,
framework, design patterns, and development methodologies. They will feel nervous if they don’t master
all of them. Or they will feel panic when people talk about
the tech, but they have no idea what it is. The fact is that no one can know everything
about development. I remember when I tried to apply for the job,
I saw a long requirement list from the job description. When I got the job, I found that some of the
skills I barely use them, or I may not even use them at all. I don’t know why some companies still keep
doing these. Maybe they try to scare away some developers
with low self-confidence. So it is ok that if you don’t know everything
at the beginning. It just takes some time for you to build up
the foundation gradually. When the junior developer gets a job in a
company, they may feel they are not good enough to stay at the workplace because other people
look very capable. Only you have no idea what to do. If you feel this way, I would say you worry
too much. Because it is not your job to judge if you
are qualified or not, it belongs to the people who conduct the interview. They are experienced people who know what
kind of people they are looking for. The company won’t pay you 50K, 60K or 80K
for nothing. Let’s say if the other colleagues are better
than you in skills. So what? If the company chooses to have you, which
means you are not that bad. Or you may be one of the best candidates already. The other people may not as good as you. Just like when I talk about the school system,
Sometimes it is not because it is the perfect system. But at this stage, we haven’t found a better
alternative, which can replace it entirely. By the way, if you want to know college is
right for you, I also made a video about it. You can find the link in the description. The fact is that you get the job already. Don’t waste your time. Try to learn from other colleagues or senior
developers. Fill in the knowledge gaps as quickly as you
can and start contributing to the team. The next mistake is that some developers try
to remember all the details. Usually, the senior developer or team lead
may make this mistake. E.g., if the junior developer asks the senior
developer or team leader questions and expects a quick answer. Unfortunately, sometimes, we may not remember
it. Some people feel embarrassed. The fact is we cannot remember everything. It is totally fine if we forget some details. I think it is even better. As I said before when to learn C#, .net framework,
and design pattern, I have read more than 100 technical books. Does it mean I read the book word by word? Or I remember all the details. Of course not. But I will remember what the mechanic is for,
in what situation we need to use it, any alternative solutions, etc. Regarding the implementation details, I am
not going to waste my time to remember it. But if there is something I need to use quite
often, then yes, I will remember it. Otherwise, I will force myself not to remember
the details because I need to save space for other relevant information. It is like virtual page technology. If you want to be more productive, I also
make a video about how to get more things done. You can find the link on the right corner
or in the description below. If you like this video, don’t forget to subscribe
to the channel and turn on the notification. Then you will get notified when I publish
the new videos. I appreciate your support. Thanks for watching, this is Lee. I will see you next time.

5 thoughts on “Impostor Syndrome Software Engineer (smash it by 3 good practices)

  • Let's smash impostor syndrome together. How do you overcome it? Please leave a comment and let me know.

    If you want to be more productive, don't forget to check this video:
    How to Be Productive as a Software Engineer | My Secrets to Get More Done!
    https://youtu.be/RNmFGWceGdM

  • 啊!感动~ 有字幕能听懂很多了~哈哈。赶蟹前辈分享~ 请问前辈用的什么视频剪辑软件?(^人^)

Leave a Reply

Leave a Reply

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

Copyright © 2019 Geted Tabs Online. All rights reserved.