Said in the previous

Hello everyone, it’s a new day.

The topic of “Some common pitfalls of self-taught programming” has been discussed in this video for a long time. Time has passed for more than half a year, there are still many partners will mention a variety of common doubts in the process of self-study, so I would like to summarize these ideas with words, and we encourage each other.

Mistake 1: Ignore the foundation, blindly into

The basics and the basics are really important. Take the Java world for example, there are so many application frameworks out there, they’re so varied, they’re so iterative. However, if the foundation of Java SE is not solid, the network protocol and operating system is not familiar, and the basic design pattern is not understood, then blindly pursuing to learn the new framework will lead to confusion and difficulty.

Solid foundation, the application of the framework of learning naturally need not be afraid, soon can cut into the core, master the principle. And the more fashionable things will be eliminated faster, after all, the iteration is too fast.

For programming development, the fundamentals that have been emphasized here mainly include: programming language itself, data structures and algorithms, computer network protocols, operating system knowledge, databases, common design patterns, and so on, but nothing more!

Myth 2: Do you doubt your ability to program by talent?

Sometimes learning setbacks, unavoidably doubt their own ability, doubt their own life and ideal, occasionally depressed true is too common.

In my opinion, it mainly depends on your experience, vision, and knowledge richness. Because it’s hard for beginners to see something behind the question, their vision is not that wide. From my personal experience, I used to practice books in the heart of some confusion and confusion, with the increase of knowledge learning, see and hear of the rich, also naturally solved the doubts.

Therefore, to some extent, this thing can not be rushed, we can only rely on efforts, accumulation, time to complete, learn a certain time you will unconsciously find that some of the original doubts and difficulties have suddenly become clear.

I still believe in one word: programming development is definitely not to the point of talent, do not doubt yourself daily, do not belittle yourself.

Myth 3: Work alone and learn in isolation

Breaking away from communication tends to make learning problems accumulate and eventually lead to losing interest and being persuaded to quit. Therefore, I think we should “go out” to study.

About this matter, I think we can actually do a lot, the simplest way is to dare to summarize, dare to share, dare to learn and do things to show and communicate with everyone, even if the criticism is received, another perspective, reflect their own defects and deficiencies, improvement is growth.

Myth 4: You must learn the best language

Or fear that you’re not learning the best language.

This is also a question that has been mentioned most frequently in my communication with my friends for more than a year. In fact, there are no good or bad languages, but only suitable application scenarios. Want to learn what also combines own interest field and target post to decide. I think it’s the latter that should be explored and clarified first.

Myth 5: What if I never remember code?

Code really does not rely on memory, but keep writing, keep thinking, in repeated practice master. If you do, you end up memorizing patterns and routines in design and coding rather than specific code.

Never try to substitute memory for understanding!

Myth 6: Collecting information but never reading it

It seems that everyone has a problem, that is to collect resources everywhere, a lot of things in the network disk, but the basic never look, also bad retrieval.

I think there is no problem in collecting data, but it is suggested to classify and mark the moment of storage for the convenience of subsequent retrieval and learning. In addition, it is also recommended to plan the learning route and time node as soon as possible, and the obtained information and learning route association, solid implementation, the use of information is the key!

Myth 7: Learning and forgetting is not a good way to learn programming?

Learning and forgetting is a common problem that most people have. The main reason for forgetting quickly is lack of use, lack of practice and practice.

So in order to overcome this problem, we can do at least: first, more records, more summary, more review. For a knowledge or skill, you can draw a brain map, or write a technical blog, these are good forms, and easy to review later; On the other hand, it is demand-driven to try to think and use the skills learned to do something small. It is very important to practice. Even if there is no good idea at present, you can also study some excellent open source projects to find ideas and inspiration.

Myth 8: Can you do programming after non-class work?

For more than a year, another very common question I have encountered is: I majored in XXX and have the intention to engage in programming development in the future. Can I transfer to my current job or find a related job?

From personal experience and can see whether their students, the school know a friend, or work colleagues, after meet professional background is multifarious, regardless of such as communication, electronics, automation professional backgrounds to make programming, and even the geographical science, confidential equipment professional I have seen, so from a certain extent, this also is nothing.

An important role of university is to cultivate the ability to study independently and solve problems independently, so there are a lot of self-taught programming and development.

Afterword.

Ok, chat so much, I hope and partners together to encourage it, refueling is over!