I think every developer in the learning process of growing up, in the face of technical difficulties, has gone through the process of self-doubt, but sometimes this is not your fault, we have experienced such a process. We, as a developer in the process of growing up, there are always some small victories and small frustration, learn to cheer for their own right.
Any of the following is not sound very familiar?
You often worried about their not good enough
Look around you developers, they seem to have everything. Their code is more concise than you, they Debug faster than you, they just need to read the documentation before coding can very well continue coding. They look confident, but also a passion for coding.
But, you're worried. You worry you not know enough about the framework and the language used, you worry about the introduction of new errors; you are worried about the hottest technology can not keep up; you worry you do not have enough talent to get it all in terms of nature. You're thinking: "Maybe I do not want to be a developer!"
If any of these thoughts of self-doubt, you sound very familiar. Well, in fact, you are not alone. Google search for "self-doubt developers" (self-doubt developers), you will get more than 200w result in less than one second.
I am you
have some time, I also experienced a strong self-doubt. It was in college, I was ready to review and interviews when it happened. These algorithms are problems every day makes me feel completely defeated. I like you, and now worried about their not good enough.
In the end, I was rewarded by practice, I received the offer from more than well-known technology companies. Along the way, I learned two important lessons changed my views on programming, eliminating the idea of my self-doubt.
I now share with you the hope that they can help you.
Lesson: Learning program and exercise the same muscle
To learn how to play, you need to go on the pitch to play; in order to exercise a stronger muscle, you need to go to the gym lifting weights; want to learn programming, you need to sit down and write code.
After lifting weights, the next day you will feel sore and tired. And when faced with programming problems, it would be very burn the brain, you will feel frustrated.
You do not give up exercise because of the pain, you know that this is part of the training process. But when you get stuck in the programming, you might suspect that you would like to know whether they are smart enough.
because:
Do you think you are stuck fault.
While others make it look effortless.
1, the jammed part of the process
Maybe no one told you, but get stuck during programming is absolutely normal, it can even happen in the advanced developer who. A large part of programming is to figure out why things happen you expected did not happen. If you feel, for the first time when children can stand up and walk is ridiculous, why would you want the first draft of your code can run perfectly without any mistakes?
I remember when I was stuck for a long time, I want to put my head against the wall. I know it's sad and frustrating (especially when dealing with issues related to the development environment). But it is hanging in here. Depth study of this issue, with Google, ask some friends, take a walk. You'll eventually solve it and move on. And as you get more experience, you will slowly get into trouble.
If next time you're stuck again, do not waste time self-doubt. You should remind yourself that it's not your fault. this is normal. This is just part of the process.
If you are a beginner, it takes several days to set up the development environment is very common, these moments might crush your soul. You try to perform according to the document step by step down, but the random errors continue to occur at every step. Document looks simple, but it is not. this is not your fault. There are people who read the tutorial 99.99% stuck. The remaining 0.01% is lucky, just exactly the same operating system environment is configured with the people who write the document.
Unfortunately, the first step in learning programming is depressed and broken hearts the most part. When you see the mistakes that you can not understand, simply copy the exact error logs and Google search. (The error log with quotation marks or search only the first half of the error log may be helpful.) To try different solutions until you find the available solutions, and then continue to the next step.
Please forgive me emphasize again: stuck not your fault at this stage. We all do it. I guarantee that once you have gone through this phase, the program will become more interesting.
2, we have "native intelligence" and "be smart" confused
In the last semester of college, my friends surprised by my performance on "Advanced Data Structures and Algorithms" course. When they are very hard to learn, I look effortless.
They do not know that, a few months before class, in order to prepare for the interview, I spent hours practicing coding challenges, covering the same topics and curriculum: dynamic programming algorithm depth-first, breadth-first algorithm. It seems effortless, simply because the course of these efforts, I have experienced.
The first time I taught these concepts, I would spend hours staring at a question of time, but could not figure out it. When I give up and look for solutions online, I try to understand them. When I finally did, I feel even more depressed because I doubt if you're smart enough, why I can not think of such a solution.
Sometimes even when I encountered the same problem again, I probably still do not know how to fix it. I would be so stressed that I had to take a long hot shower to cool off.
So, when I say I know I doubt yourself, worry about their own time can not, believe me. I used to like this. I can assure you, you are not alone, many great developers have experienced the same thing.
The next time the people around you when outstanding performance, while you are struggling hard, do not think you do not have enough talent. Most likely, they just earlier than you come into contact with the subject or similar subjects. Their brains have established a "muscle" to deal with this type of problem. After a struggle now, you will look smart and relaxed.
This is the same as our common sense.
To exercise your muscles through exercise. The more effort you put in, the longer the training time, the stronger your ability. Learning programming have exactly the same process. The more time you spend, the more you will be proficient. you get what you sow.
Lesson: Focus on your technical ability, rather than their own
Do not think about how good you are or how a bad programmer. If you are in the last 5% of the team, you want to get better. If you are fortunate enough to enter the top 5%, you still want to get better. Whether you are good or bad, always someone in front of you, but also someone behind you. So why waste time thinking about this problem?
Instead, focus on your technical ability. Do not ask how good you are, ask how good your code. You should be thinking about how to make it better, faster and more readable? Long-term focus that make you admire engineer, read their code to see you any different? They recently what new stuff is studying?
If you are already a software engineer, then someone will pay you to write code. You should stop and reflect, because it means a lot: it was either trust your coding skills, or see your potential. To do this, the only way is to focus on your technical ability, continue to improve.
Record your little victory!
The last time you were stuck, not sure if that resolves the problem. And finally, how do you solve?
Open a new Google document and record it down.
The next time you doubt yourself, look at this document, and remind yourself: If you can solve the problem last time, you will solve this problem.
Use this document to record the challenging issues to overcome your process and what you learn, and always celebrate these little victories, with these small victories to motivate yourself!
If you are reading this text, leave comments, to share the last moments stuck to remind those who are struggling, they are not alone!
At last
Day by day off really fast, often feel time moving forward, and we are still stagnant, seemingly trying to learn the daily work, think about it in fact will find that the day we seem to really did not do anything, seemingly busy day, we put the time spent on what? Learn! But why do I feel that it learned nothing? In fact, not without learn something, but only our learning efficiency is too low!