Some netizens asked questions on the Internet: Can I still become a tech master after switching to another profession to learn programming?
While receiving comments from many netizens, many netizens also asked:
1. If you can't become a technical expert, do you stop learning programming?
2. Learning is a lifelong matter, where did you come to become a monk? Learn programming at the age of 25. At the age of 35, you are someone with 10 years of programming experience.
3. In the Internet age, there are too many cheats everywhere, and there are too few sincere practitioners, which has nothing to do with whether or not they were born in a major. Some people kill other people's courses for two years in four months.
4. I don't know if you can become a programming master or not, but what is certain is that your unremitting efforts will definitely bring unexpected results. Don't care about the result before you pay. Is it because there is a 1% chance that you will get stuck when you eat fish, so you won't eat it for the rest of your life? If you can't become a big cow, you won't learn programming? If your partner can't promise you to grow old together, you won't fall in love?
It is true that no matter what you do, to achieve a certain desired result, it requires time accumulation and firm belief. If you have no confidence in yourself at the beginning, how can you do it?
01Why
be a programmer
There are many such questions on the Internet, and the answers are even more diverse, but among them, "high salary", "good job search" and "professional development" are the most mentioned.
02
How programmer wages
Randomly select a few programmer-related positions on the job search platform to search, and found that the salary is indeed not low.
(The above data source: Shiyou Ji)
03
on the way to learn how to switch to programming fore
An interesting phenomenon: More than half of the trainees who participated in the training at LeByte are college graduates, and some of them are majoring in computer science.
When asked why they still have to go to training courses after graduation, the answers of these students were similar, because they did not master the necessary abilities in the four-year university.
In the workplace, contrary to prestigious schools and academic backgrounds, there are many programmers who are "studied halfway" in non-disciplinary backgrounds, and they have become the backbone of the team and the big cows in the eyes of colleagues.
Therefore, prestigious schools and courses are not as unsurpassable as imagined. After all, in the workplace, no one can rely on these reputations for a lifetime.
04
How to learn programming when changing careers halfway
1. Before learning, figure out what program you want to write
Learning to program is basically learning to build things. If you know what you want to build, then the road to programming learning will suddenly become clear. Only after you understand your goals can you devote yourself to learning with a purpose and pertinence.
If your goal is only to "learn to program", but you don't know what kind of programs you want to write, or how these programs will be used in work and life, you are likely to feel that programming learning makes you frustrated and frustrated. .
2. Programming is not at all mysterious, not difficult at all
There is no essential difference between programming and other skills. Just like language learning has grammar and vocabulary; like mathematics, there are different steps and different topics; like all skills and crafts, programming also has skills, tools, and good habits for different tasks summarized by predecessors. .
3. In case of frustration, tell yourself: no one can do it at once
When you first learn to program, you will soon run into this problem.
You feel that you have configured everything, check it and check it again and feel foolproof, dreaming that it is the time to "witness the miracle", but suddenly you get slapped in the face by the bug. How to modify, you have no clue, and the frustration that you can't start makes you want to give up again and again.
This kind of experience is normal for programmers of any level. Having this kind of experience does not mean that you have any problems with your IQ, technical savvy, or your suitability for programming. No matter if you are a programmer or a programmer, you will have this experience.
Tell yourself: Bugs are normal, no one can fix them all at once!
Tell yourself: The reason for the error is logical and identifiable, and any problem can be solved. You can talk to other people in the team, or ask your seniors for advice, usually you can find a solution.
4. Persistence is more important than method
There are many articles about "correct programming learning method" and "best programming learning method", but not many teach you "persistence".
In fact, to learn programming, persistence is more important than method.
No matter what programming class you study, you will have such a period of "hit the wall". The only solution is to stick to it.
As a programmer, you must constantly learn new skills, try new things, learn new knowledge, and constantly discover and solve problems. Only by "persistence" can you become a real "big cow" after years of suffering and tempering.