When conducting relatively simple learning, experts or teachers often give beginners such as learning Java as an example, beginners best learn C language, master basic language concepts; then write Java version of HelloWorld, then learn basic Java.lang, java.util library, constantly understand the concept of OO during the process of learning; then learn from the network, ui, web, etc.
Obviously, this is an arrow-shaped linear learning map. However, there is actually no one's purely relying on these suggestions or guidance to learn success, and ultimately the result is often two results: one is the learning process is boring, and finally give up or rely on perseverance struggle; one is in the process of studying. Knowledge, repeated confirmation reference, ultimately its music is made.
Most people are in the second state, or they don't conscious this, the more obviously reflected in the accumulation of workers. The brain is a circle, you need to learn to stimulate him to expand, linear learning ideas will violate geometric laws, and ultimately let themselves exhausted, full of frustration.
Therefore, learning, constant learning, is not limited to technical learning. This is particularly obvious in the Java field. Spring's core author Rod Johnson is inconsistent with the technology in music, and most domestic J2EE technology is a philosophical background. Therefore, it is necessary to constantly study, not only to the technology world, the technology in the open source is always sensitive, but also to spend time to enrich the accumulation of other aspects. One day, such as a sense of inspiration in literature will make your design amazed; or you can make more optimized at the table ball.
Learning and age, it is related to inertness, so, keep learning, live to old, learn to be old. The network learning process is not limited to the learning vision of the industry, and the accumulation of constant experience will make learning truly happiness. -------------------------------------------------- ---------------------- ps: I have been touched. Indeed, I was originally used to learn things in a straight line study. The study plan I have recently developed is also the case. It seems to be changed. I divide my program into two parts. In the big direction, you can contact the knowledge of software engineering, although I think I may not understand all. I want to learn a specific tool by learning VB and use it to make a specific tool to understand the entire framework developed by a program. Then, under this large frame, learn OOP, learn the data structure, and learn algorithms.
