What is the sequential step of learning programming?

What is the sequence of learning programming? Learn programming not only need to adhere to, strong logical thinking, but also have a perfect learning programming method, the following small Lego to bring you to learn programming methods, for beginners believe that the program will have a great help!

The seven stages of learning programming are required. As follows:

1th phase

Opportunity you are very happy, you always want to learn this new content, such as a programming language, whether it is a planning or environmental forced, in short you finally have the opportunity to learn.

2nd phase

No base for optimistic Google search--pick one or two tutorials that are of interest to you, buy materials and books, and then start MOOC (large-scale online open tutorials). Tutorials are fun, and even online repl can let you play and you feel you are progressing. Of course there are also troubles-fingers are not skilled, but you insist, refused to give up, and ready to your first project to March.

3rd Phase

The deep pit of despair you start from "Hello, World", for example, first to change the content to "Hola,mundo" such a careful attempt, and then a little bit fat, began to unscrupulous-so, error message, stack trace, random behavior. Even if you don't have all the wrong messages, the code that works in the tutorials, you may have a blank slate. You suddenly find that even some seemingly stupid but benign nuances can cause storms, turn you into a ditch and sink into a deep pit of despair. Even the simplest tasks make you miserable, and you begin to doubt yourself that you have no programming talent at all.

4th phase

Lower your body slowly, through experimentation and false baptism, you begin to accumulate knowledge little by little, by asking for help from co-workers, StackOverflow, and blogs. You begin to understand how to display data, how to communicate with databases, how to create interfaces, and how to override methods. While you can't really understand the workings of any of these, it's a little easier to keep mastering these magical spells and expanding the field of knowledge while accomplishing certain, necessary tasks. For some spells, you may use very smoothly, even in some problematic cases also mechanically, feel as long as the completion of the good, even if the heart know that they do not right. Debugging is a kind of setback exercise. Whether it is because the ego feels that the goal has been achieved, the plan is to put time elsewhere, or because it is too difficult to daunting, or that the self-proclaimed has mastered the expertise to make the choice of sensible, in general many people stop at this stage.

5th phase

The dawn arrives at this stage, and as you have accumulated enough pieces of information, you begin to find the connection between them. You begin to be able to apply knowledge flexibly, rather than mechanically, as before. You begin with the so-called intuition of some basic rules and begin to shift from rigid adherence to receiving knowledge. It's also an uneven process--and it may still be confusing to the other side--but you have the confidence to take it one step at a time, and you begin to enjoy the process.

6th phase

After a professional period of time, you fully mastered the basic model, began to feel that programming is like eating as easy as natural. You can intuitively understand how things work and easily mediate between architecture, coding, and debugging. Generally you don't have to think about problems as much as you go from home to shop-you know where to go, and if you have some new roads, you can instantly weigh different options and choose the best route. At this point, the hardest thing to do with the problem is the problem itself, not the operating system to support what you want it to do.

7th phase

Achievement you are now an expert with years of experience. The time and energy you put into it is rewarded. You write blog posts, help open source projects, become the peer recognized experts. It becomes your identity and honor, and it becomes your yoke, and what you do needs to match the name of the expert. Suddenly one day, the new thing appeared. You know in your heart that this new thing is good, it will be useful, and it will be a trend in the future to help ease the problems that existing tools don't solve. But at the same time, you clearly know the effort and time required to become an expert, need to feel inadequate and frustrated again, need to go to others for help and so on, you do not want to, you flinch. You'd rather close your eyes and get stuck in a rut and curl up in a group like withered stems slowly die.

Note : For more wonderful tutorials, please pay attention to the Triple design Tutorials section,