Some insights about learning programming - not forgetting early heart

Order
accidentally saw previously worked on with the students to write technical articles today, we learned more active in blog github and technical exchange forums and above. Look back at himself, as if still remain in the way it was before, it seems like a lot of really practical techniques disparity.

Originally I thought I had to learn very rhythmic, and now it seems he still stays in the stage slowly forward. All this really is like a wake-up call, and instantly my heart there is no small vibration, perhaps it is time to face your own current problems, take a look at the kind of love of his past pursuit of technology in the end how much left.

Found himself pursuit of technology is not enough
to learn too cluttered but not deep enough
show no clear plan in learning technology, each time learning technical articles are a Mo Kanwan, which saw a technical point jump another piece of technology article went. Although the cause read many articles, but the results are only a rough contact with it, and there is no practical significance, resulting in a waste of time but did not accumulate knowledge.

Requirements
• develop a learning plan, in accordance with the learning path step by step, from shallow and deep, rather than picked up the one to see.
• see technical article, must be clear purpose, to consider the issue in conjunction with content, improve thinking technology can bring, as well as the direction of possible practical applications.
• actual coding of the project, do not empty to see more, be sure to test their actual coding, but there must be technical summary or text output after completion, the other can, it is best to read the official wiki and project implementation logic source.

* To develop good habits of
learning technology should pay attention to build comb and knowledge of the context of the structural system, most of the time he pulled an article to see, did not classify carding After reading it, not any summary after reading, resulting in no how much practical effect.

Requirements
• Each time code output to push on github, it was not required to start or browse the main facilitate their management first.
• Consider including translation group, co-translation of foreign advanced technology articles.
• usually know almost at the point above can also be active, with the big cattle more than the exchange of technical problems.
• summary notes and combing habits

• how the initial process does not require high quality output of articles, first to develop a habit, how many people are not required to read the article, but must have. The same is not required as the students create their own personal blog page, first written in csdn and Jane books, then we can strive efforts in that direction.

Goal
to find his love of technology, not forgetting the beginning of the heart, keep a beginner's mind, for the simple desire and longing technology, hoping he can rediscover the heart really want to own.

mutual encouragement!

Guess you like

Origin blog.csdn.net/PyhtonChen/article/details/94621910