Years of summary, some core suggestions for learning programming

Hello everyone , I am a yes.

I don't know how you set foot on the road of programming , I was attracted by the hackers in the movie , Only then chose the soft engineering major ( It's actually a second major , ha-ha ). I thought I could put out the lights of a building like the hackers in the movie in the future , Manipulate the broiler to attack . Who knows, in the end, he became a CRUD Boy.

But fortunately , In the end, I still love programming , From the beginning, I was ignorant , Up to now, I have entered the industry , Programming can be said to have been deeply engraved in my mind .

Now that we have set foot on this road , Then go on well , I have also studied programming for many years , Today, let's talk about some of my core suggestions for learning programming , throw away a brick in order to get a gem , Welcome to discuss ~

Good at searching

Whether it's a beginner or a Daniel who has been working hard for many years , Being good at searching is the most important thing in my opinion .

In this day and age , It can be said that as long as you can search, there is no problem that you can't deal with ！

Never decide , Search engine .

Programmers work for search engines , Whether you are Google 、 Bing or Baidu , It's better to search than to ask others in the Group .

Up to exception handling , Down to the analysis of principle , Online , If you can't find it, it's your personal problem , You can wait for my next article 《 How to make better use of search engines 》

Active learning

That's true. , This time is different from the past , There are too many videos on the Internet , Too many blogs can learn .

For video , I think I'm very friendly to beginners , It can be explained in a dynamic form, which is easier to understand , But watching videos after getting started is too slow , So I personally think video is more suitable for beginners , For example, learning Spring 、SpringBoot And other frameworks can be used to watch videos .

For Blogs , There are many great God blogs on the Internet , I also recommended several Blog websites before , But few can give you systematic learning , What's more, there is a surprise , Here's a surprise , Therefore, systematic learning is still lacking .

For books , Easy to read , also More systematic , And after years of filtration , Some classic books have come to the fore , You can enjoy it with peace of mind . For the students after getting started , You can learn relevant knowledge more quickly and comprehensively , recommend .

So I personally think ：

• Video viewable , Introduction and some open courses of computer foundation , Excellent .
• Blogs are available , Fragment time assault , Excellent .
• Books must be read , Long and systematic learning is indispensable .

by the way , If you read a lot of books , You will find many articles and videos on the Internet , They all copy books .

How to write code

No matter how much you know , After all, it has to be converted into code to bring benefits .

So don't forget to write , Take any opportunity to write . For example, when encountering a mechanized repetitive work , Just want to write a gadget to replace it , The code is used for this purpose .

If you work for many years , You should be able to understand the kind of code complexity at work , It can only be said that after being familiar , Probably most people can write with their eyes closed , So in addition to daily work , You can write something interesting , Apply what you have learned “ New knowledge ”.

Writing code for yourself is arbitrary , Write what you want , Use whatever you want , Just play ~

And play ~ It's critical for those of us who write code , It can arouse your interest , Satisfy your sense of achievement , Let you go further .

And write more , There are many problems , Practice makes perfect , Then I have experience when I encounter something , Others searched for a long time , You solved it directly .

Programming , How to call programming if you don't write ？

Write more about this , I didn't do well , Encourage them together .

Basic skill

Although I'm from a major , But my basic skills are very poor .

Just after graduation , You ask me what binary tree I am ignorant , Yes, but I can't at all , A reverse linked list may be hard .

For the understanding of computer network, I had three handshakes , Four waves , confound with HTTP and TCP The relationship between , Let alone operating system memory management , What is the principle of computer composition .

Later, I can only make it up desperately , Complement data structure and Algorithm , Supplement computer network , Supplement the operating system , Complement the principle of computer composition .

These are the cornerstones , Whenever you encounter some knowledge points that you think are deep or detailed, they are related to these , For example, pseudo sharing , Network tuning , Optimization of threading model, etc .

Ten thousand Zhang tall buildings rise from the ground , Want to go far , The foundation needs to be laid .

Problem troubleshooting

For the troubleshooting of problems, we should divergent thinking , Don't knock in one place . For example, the same entry attempts many times , Just don't believe in evil , I always feel like I will succeed next time , There is no the .

Find out the context when troubleshooting problems , Take a general view first , Infer from the problem that bug The place of , And then break each one . That is to say, we need to have macro consciousness , Dare to assume , Careful proof , Try it one by one , Make good use of exclusion .

If you spend a lot of time and can't find a solution , I have a method here that works wonders .

That is to give up first , Wait a while , For example, come back to this problem tomorrow , It may suddenly become clear , Close test effectively , In the final analysis, the thinking at that time was imprisoned , I can't jump out by myself , Then leave it to time .

Sometimes, joint troubleshooting with colleagues is required for problem troubleshooting

Something went wrong. , First of all, doubt yourself . This is not just for programming , It is also a way of dealing with people “ The laws of ”.

Fully review your own code , Try to test under different conditions , Make sure your logic “ correct ”, Then doubt others .

Don't start by saying that someone else's code has a problem , draw , Put yourself in other people's shoes , If others throw your face as soon as they come up , How do you feel .

Before questioning others , Explain to the other party that you have checked various situations in the code , The problem should not be in yourself , A reasonable explanation , It will make the other party comfortable , Will let him cooperate well with your investigation , Only in this way can things proceed smoothly .

Hello , I am good. , Hello everyone , It's really good .

Last

Now that you have chosen the way of programming , Self study and lifelong learning will accompany you .

In the era of information explosion , I know it's too hard to keep learning , There are too many temptations , I hope I can work hard with you to achieve the future , Self-motivated forward .

Last , I wish you all a lot of hair , Many year-end awards .

---

I am a yes, See you next time ~