How to learn new technologies (replication)

"I want to learn rails, is there a recommended primer for Ruby?" 」

"I want to learn Android, What is the level of Java mastery that can begin? The

"I C + + has not yet started , can you learn python directly? The

Learning a new language, or a new technique, is not so much an ability as a method. What kind of person, or in what stage of life, is the highest learning efficiency? The best effect? The answer is obvious: infancy. My daughter, who is less than two years old, estimates that she now has dozens of nouns, 10 verbs, 35 adjectives and prepositions, but no fewer than hundreds of words pop out of her mouth every day. Think about how many years of English we have learned in order to speak completely from the mouth: "Hello everybody, so glad-see-you", Junior? High school? Or college? Think about how much we can communicate and communicate when we have a 3,000 word volume?

"father hug small Treasure" For Comfort

"Xiao Bao to drink grandma"-hungry

"if Xiao Bao is not obedient?" You talk to her after you've learned a rhetorical question. She's going to give you a military.

"goodbye so Long farewell my friend"-with music lesson, selling Moe

Most of the sentences, she doesn't know the meaning of each word, but she knows the vague meaning of the sentence, and from the adult's reaction, she can know that she understood the meaning is correct, so, again and again imitation, trial and error, get feedback, constantly accumulate their directly can use the "knowledge."

> This is a pragmatist's way of learning: bypass obstacles, go straight to the subject, focus on what you need to learn right away. A few years ago, before I began to learn something, I would surf the internet and pick up almost all the books I could find from the beginner to the advanced to the expert, and after looking at a whole bunch of different comments, I was content to sift through so-called "boutique" purchases and put them on the desk, as if it were a necessary ritual before learning. But this is only the achievement of the watercress and Amazon, piled up books often in my heroic view of the first chapter X (x<=5) was shelved. Later I found that I was so-called "learning to first systematically lay a solid basic skills" pit-I kept falling into the "basic knowledge" of the mire, the deeper the deeper, the more bitter, can only struggle. As a result of this struggle, 80% of the situation became abandoned.

Software development is a craft work, its learning is not a variety of knowledge may be seldom used in a brain accumulation, we can not be prepared after all theoretical knowledge ready to start learning. Scala's authors have criticized Java's inefficiency as saying that Java has made it a ritual to write programs, so there is no fun. So, when we were at the table full of books from the beginning to the experts, did it turn the study into a solemn ritual? What is important is not how much knowledge is piled up, but how it is learnt.

It's not enough just to focus and go straight to the subject. You need to practice a lot and get feedback during the learning process.   Babies do not speak until they have accumulated 3,000 words, but when the body and brain are ready for the first day to speak, and, despite all the mistakes, they are still more and more brave, repeatedly defeated war. In the same way, when you learn Python without using Ipython in the REPL environment to try a variety of skills, when you learn Django without starting a Web project to build a run, the learning efficiency is not high, the effect must be so-so. In the gym, even if you watch the coach's movements 100 times instead of trying them yourself, and accept the other's corrective advice, you still can't grasp the correct action essentials. I've seen people knocking the examples of the book into the editor, all running correctly, and then being satisfied that they "mastered" the technology. As everyone knows, this "exercise" is not a valuable exercise. We need to try and be wrong, like a toddler, to imitate, to move, to fall, to climb up, to move. Making mistakes is part of learning, and when you're finished with the content described in the tutorial, you can conceive an app or a usage scenario yourself and write it from scratch. You will find a lot of questions that will deepen your understanding of the tutorial. Questions that cannot be answered can be sought from the community, and most of the issues related to development can be resolved on StackOverflow. With this constant practice and feedback, your development skills will improve quickly. Many non-systematic knowledge and abilities (and even insights) are learned through constant practice and trial and error-they come so quietly that others see it as a gift to you, except you.

So, when do you need to learn it systematically? When you have the skills and experience necessary for the actual combat, you need to make a distillation of what you have learned on a macro level, or when your actual combat ability encounters a bottleneck. It's a good thing to say: You don't need to be a good Ruby engineer to use rails, but if you want to be a good rails engineer, you have to master Ruby well. Unfortunately, many beginners have the problem: to get a quick introduction to a technology, but using a systematic approach to learning, has not yet started, it fell on the road of hard practice.

How to learn new technologies (replication)