Some nagging about the program Ape (Turn)

In this line of programming, I've been working for more than 20 years. So far, I have written almost six or seven introductory courses in programming, with a total of more than 1000 hours of teaching time. Here's what I've emphasized more than once to my students, the crystallization of a series of wisdom I've had over the years (no specific meaning in order).

first of all, you are welcome to become a programmer.

programming is really hard. No matter how good you are at programming, the only thing that can be an obstacle is the ability of everyone to learn and solve problems. The longer you soak in this line, the more you understand the fact. This is actually very interesting-because then we will never be in the same place and content with the status quo. If you lose that aggressiveness, it's easy to get bored and even give up when it happens.

programming is also one of the most frustrating things. In general, the normal programming experience is this: try, fail, work harder, rethink, brainwave, and ultimately succeed. It's normal to be frustrated in the process, and once we're done, we're going to try to do something more difficult, and the frustration is lingering. But it will prompt us to work harder to solve the problem and arrive at a satisfactory answer. But before we do, we have to adjust ourselves and stretch our mood of gloom and blanket.

no matter how complex the problem, there will always be a solution. As we improve our programming capabilities, we will be more confident about ourselves. This helps us to adjust the negative emotions in a timely manner and to better solve the problems (say, if too simple is not a challenge).

When we were kids, we were always in trouble, but as we grew older, we had little chance of actually smashing one thing. Keep in mind that programming is not something that everyone can do. So, you're a cow!

During the programming process, the first one hours and the 10th hour are different, and the first 10 hours and the 100th hour are not the same. I remember someone who used to describe golf in a blog for the 10,000th hour, it would produce a qualitative change, as well as programming.

programming is like magic, we are all wizards. You see, we study hard, specialize in our course knowledge (computers and networks), and then summon our Magic (program). Wizards can teach other people how to use magic, and the magical devices we invent can be used by anyone (like the internet and mobile phones). All of the features provided by these devices are inseparable from the skills of our programmers.

effective use of network resources. Every problem you encounter in your first year of programming, you may have had 100 of people close to it before you, and there's definitely a variety of solutions on the web. The faster you learn the skills to search effectively online, the faster you will be learning. Warning: Do not use these network resources easily before you know how a piece of code works.

as programmers, we should not forget our toolkit at any time. These tools are our one-off. The first thing we learned in this field (variables, loops, etc.) is like a screwdriver and a hammer. These tools will accompany us every day in this world. And with the growth of our experience, we can also learn more advanced tools, which are not very popular, but are more adept at solving specific problems (such as binary tree data structures, a *, Valgrind, debuggers, etc.). Most programming areas (game development, web development, database) have their own unique set of problem-solving patterns.

The program is born out of code. On the computer, we can enjoy the other people write the scheme, can be used for reference, can be modified, can also be edited, arbitrary.

The best way to get better at programming is to write code and write a lot of code. Efforts always have a harvest. As an educator, I will do my best to give you a hand. However, if you have mastered enough knowledge, then as long as there is sufficient time, no I can also find the problem. The old saying goes, "persistence is victory." So, practice writing code, it's the year.

At the same time, we also need to read a lot of code. There are a lot of programmers in this field than we, they have written a lot of code to reference. Three people, there will be my teacher.

It is said that the second programming language is always the hardest, because the first door restricts the way we think about the program, and when we need to learn another programming language, we have to break the original order and re-establish one. After learning a second language, it's much quicker to learn another new programming language. Now, I can do almost any given programming linguistics in just a week.

there will never be so-called"the best". Some languages and tools are better at solving certain problems. When we learn other languages, do not try to use the old port to connect to the new system, to use the new language to think and solve problems.

Learn to enjoy yourself. Programming is a large collection of problems that need to be addressed. Give yourself a little fun, you can write some of your own interesting programs, interest is the best teacher.

Good programmers will never be satisfied with the status quo, always learning. If you can do this, then you never have to worry about your job.

When you have a problem, you can try to write the program on paper. This is not a joke, this trick is usually I don't tell him.

Finally, I would like to say that there are many other good suggestions that I have not talked about-but, I want to say, the best advice is that we have to find the right one.

I hope you can have a happy heart programming, happy to write code

Some nagging about the program Ape (Turn)