The following is a flowchart of "Teach Yourself C ++ in 21 days". Please read it carefully. If necessary, you can view this book for reference: http://www.china-pub.com/27043
After reading the picture above, I was thinking that I have been studying C ++ for 12 years. It seems that C ++ has not learned much about it. I think STL and generics are still very big. However, I should consider studying quantum physics and biochemistry so that I can go back to 98 years to kill me who are still in college and reach the goal of C ++ in 21 days. In addition, we should remind our friends who have just begun learning C ++ to be careful when they were killed in 21st days. Haha.
Of course, it takes a long time for you to learn a technology to spoof such images. As shown in the third and fourth pictures in the video, it takes you ten years to keep trying, sum up the lessons learned from errors and learn from each other in project development. Only in this way can you really learn.
Here is an article titled 《Teach Yourself programming in ten yearsSomeone has translated the text on the Internet, but the original text has been updated. I will repost the online translation and update it as follows:
Learning programming in ten years
Peter norvig, why is everyone impatient? When you walk into any bookstore, you will see a long row of similar books next to "Teach Yourself Java in 7 days" (7 days without a teacher, they want to teach you Visual Basic, windows, the Internet, and so on, but it only takes a few days or even hours. I performed the following search on Amazon.com: pubdate: After 1992 and title: days and (Title: Learn or title: Teach Yourself)
(Published on: 1992 and title: day and (Title: or:) I got a total of 248 search results. The first 78 are computer books (79th are "Learn Bengali in 30 days", and 30 days are used to learn the bengale language ). I changed the keyword "days" to "hours" and got a very similar result: this time there were 253 books, and the first 77 were computer books, 78th is "Teach Yourself grammar and style in 24 hours" (learn grammar and style 24 hours a day ). 200 of the first 96% books are computer books. The conclusion is that either people are eager to learn computers, or they do not know why computers are surprisingly simple and easier to learn than anything else. No book is meant to teach people a few days to appreciate Beethoven, quantum physics, or even how to dress up a dog. In 《
How to design programsIn this book,"
Bad programming is easy. Idiots can learn it in 21 days, even if they are dummies ."(Bad programs are easy to learn, even if they are dummies and idiots, within 21 days .) Let's analyze the meaning of a question like "learn C ++ in three days" (3 days to learn C ++:
- Learn: In three days, you have not enough time to write meaningful programs and learn from their failures and successes. You don't have enough time to work with experienced programmers. You don't know what it is like in a C ++ environment. In short, there is not enough time for you to learn a lot. Therefore, these books talk about superficial proficiency rather than in-depth understanding. As Alexander Pope (English poet, writer, 1688-1744) said,It is dangerous to know half the solution (a little learning is a dangerous thing)
- C ++: In three days, you can learn the C ++ syntax (if you already have a similar language), but you cannot learn how to use it. In short, if you are, for example, a basic programmer, you can learn to write a basic-style program in C ++ syntax, but you cannot learn the true advantages (and disadvantages) of C ++ ). Where is the key? Alan Perlis (first Chairman of ACM, winner of the Turing Award, 1922-1990) once said:"If a language cannot affect your thoughts on programming, it is not worth learning.". Another point is that sometimes you have to learn a little bit about C ++ (more likely JavaScript and flash flex), because you need to access existing tools, used to complete a specific task. But now you are not learning how to program, but how to complete the task.
- 3 days: Unfortunately, this is not enough, as described in the next section.
Researchers studying programming (bloom (1985), Bryan & Harter (1899), Hayes (1989), simmon & Chase (1973) in the past 10 years have shown that in many fields, it takes about 10 years to develop professional skills, including chess, composing, painting, piano, swimming, tennis, and neuropsychology and Topology studies. There does not seem to be a real shortcut: even if it was Mozart, he was 4 years old and showed a music genius. It took him more than 13 years to write world-class music. Let's look at another music type of the beaters. They seem to have suddenly taken the lead in the 1964 Ed Sullivan program. But they have been performing since 1957, and even though they have been very attractive for a long time, their first real success-sgt. Peppers-will not be available until 1967. The Malcolm Gladwell study reported that the students in a class at the Berlin Conservatory of Music were divided into high and low levels by level, and then asked how much work they spent on music exercises:
In these three groups, each person starts to practice at the same time (when he is five years old ). In the first few years, everyone practiced for 2-3 hours a week. However, at the age of eight, the exercise intensity began to show differences. The best people in this class start to practice more than others-at the age of nine, six hours a week, and eight hours a week at the age of twelve, when I was 14 years old, I had 16 hours a week and practiced more and more during my growth. by the age of 20, I had to exercise for over 30 hours a week. By the age of 20, these excellent people spent more than 10,000 hours practicing music in their lives. In comparison, the average number of other students is only 8,000 hours, and the number of students who can only stay as teachers in the future is only 4,000 hours.
So it may take 10,000 hours, not ten years, but it is a magic number. Samuel Johnson (British poet) believes that 10 years is not enough:"
Excellence in any field can only be achieved through a lifetime of effort; a little lower price cannot be changed."(Excellence in any department can be attained only by the labor of a lifetime; it is not to be purchased at a lesser price .) chaucer (English poet, 1340-1400) also complained:"
It takes so long for you to master your skills.(The lyf so short, the craft so long to lerne.) Below is my recipe for success in programming:
- Interested in programming, programming for fun. Be sure you will always be able to maintain enough fun, so that you can invest 10 years in it.
- Talk to other programmers and read other programs. This is more important than any book or training course.
- Programming. The best learning is to learn from practice. In a more technical language, "the highest level of performance of an individual in a specific field is not automatically obtained as a result of long-term experience, however, even very experienced individuals can improve their performance through deliberate efforts." (P. 366) and "the most effective learning requirement is to develop appropriate difficult tasks, meaningful feedback, and opportunities for repetition and Error Correction for specific individuals ." (P. 20-21) Cognition in practice: Mind, mathematics, and culture in everyday life (cognition in practice: Culture of mind, mathematics, and daily life) it is an interesting reference book on this point of view.
- If you want to, spend four years in college (or several more years as a graduate student ). This gives you entry-level qualifications for some jobs and a deeper understanding of this field. However, if you do not like to enter the school, (make a sacrifice) you can also obtain similar experience at work. In any case, learning from books alone is not enough. "Computer Science Education won't make anyone an expert programmer, just as studying paint brushes and paints won't make anyone an expert painter." Eric Raymond, the author of the new hacker's Dictionary (new hacker dictionary) said. One of the best programmers I have ever hired has only a high school degree, but he has created many great software (xemacs, Mozilla) and even discussed his own newsgroups, in addition, stock options allow him to reach the level I cannot reach (the author of Jamie zawinski, xemacs, and Netscape ).
- Complete the project with other programmers. Become the best programmer in some projects; be the worst in some other projects. When you are the best programmer, You need to test your ability to lead the project and inspire others through your insights. When you are the worst, you learn what masters are doing and what they don't like (because they ask you to do those things for them ).
- Take over other programmers to complete the project. Understanding the programs written by others. Let's see what the program needs to be understood and modified when no original programmer is present. Think about how to design your program to make it easier for others to take over and maintain your program.
- Learn at least half a dozen programming languages. This includes a language that supports class abstraction action (such as Java or C ++) and a language that supports functional abstraction (such as LISP or ml ), A language that supports syntactic semantic action (such as LISP), a language that supports descriptive specification (such as Prolog or C ++ template ), A language that supports coroutine (such as icon or scheme) and a language that supports parallelism (such as sisal ).
- Remember to include the word "computer" in the phrase "computer science. Measure the test taker's knowledge about how long it takes to execute a command on your computer and how long it takes to obtain a word from the memory (including cache hit and miss ), how long does it take to read continuous data from a disk and to locate a new location on the disk. (The answer is here)
- Try to participate in a language standardization work. It can be an ansi c ++ committee, or it can be used to determine whether the coding style of your team adopts two spaces of indentation or four. Either way, you can learn what people like in this language, how much they like it, or even why they have such feelings.
- Have good judgment from language standardization work as soon as possible.
With these ideas, I doubt how much I can learn from the book. Before my first child was born, I read all "how ......" But I still feel like I am a newbie with no clue. 30 months later, when my second child was born, did I pick up those books and review them? No. On the contrary, I rely on my own experience to make the results more useful and reliable than the thousands of pages written by experts.
Fred Brooks, in his short article "no silver bullets" (no silver bullet), sets out three steps to discover outstanding software designers:
- Identify the best designer group as soon as possible.
- Assign a career mentor to take charge of the development of potential objects and help him maintain his career resume with care.
- It gives growing designers the opportunity to interact and inspire each other.
In fact, it is assumed that some people themselves have the necessary potential to become outstanding designers; all they have to do is to guide them forward. Alan Perlis is more concise: "Everyone can be taught how to sculpture, but for him, what can be taught to him is how to avoid sculpture. The same is true for outstanding programmers ".
So even if you buy those Java books, you may find some useful. However, your life, or your real professional skills as a programmer, will not actually change within 24 hours, 24 days, or even 24 months.
(Full text)
Http://coolshell.cn/articles/2250.html
