Myth 0 1, programming depends on talent.
You may have such a question: are all beginners in programming, why is the progress of learning programming so different?
Many people will think that this difference is caused by talent. In fact, this view is wrong For most people, the reason for the difference in learning progress is more in dry environment than talent.
Myth 02, learning programming is to be good at mathematics.
Many people will equate mathematics and programming directly, thinking that learning programming requires good mathematics;
Or think that programming is like complex calculus in the field of mathematics, which needs to be modeled with mathematical knowledge.
These views are all wrong. We only need to master basic mathematical knowledge before we can start programming.
Many complicated mathematical calculations can be handed over to the program to operate. Learning programming well can even help you better understand the abstract concepts of mathematics.
Myth 03: Just read and don't write.
In the process of learning, do you spend a lot of time watching videos and documents, but seldom spend time writing your own code? If so, you have entered another misunderstanding. Just like learning to swim, you can't really learn to remember movements without practicing. The same is true of programming. No matter how familiar the conceptual structure is, it is difficult to write the correct code.
Myth 04: Reciting Documents
When I first came into contact with programming grammar, many novices were used to memorizing programming grammar one by one by using the methods used in school.
But programming is not an exam, so we don't need to memorize knowledge points that are easy to find and not commonly used.
Because any popular programming language has a complete document, and the document is like our Chinese dictionary, we don't need to recite the dictionary at all.
Programming is also a truth, we don't need to memorize documents, as long as we have the ability to consult documents, we can solve most problems of programming and even development.
Myth 05, afraid of reporting mistakes
Novices are always overly nervous when writing code cases: they will be happy to see that their code has not been reported as an error, and then protect this code for fear of accidentally moving something to cause an error. This change of heart bond status is wrong.
Don't be afraid of code error reporting, because error reporting can let you know more about the abnormal state and problems of code programs, and also let you learn more ways to solve the problem of error reporting.
The fact that there are no errors in the code does not mean that the code is perfect, nor does it mean that you have mastered the knowledge points of this case.