//I remember that when I was a freshman (12), I came into contact with the textbook of C language, which was his book. It was really tragic then. More than half of the people in our class failed this course. Think about what this concept is. His book is really ugly, with too much theoretical knowledge and lack of practice and examples (compiler environment will lead to differences in running results, but it is not pointed out). In a word, this book is harmful.
//But, after all, his active age is different from ours. There were not many people who could program at that time, so his book was reasonable, but it was really not very friendly to beginners. When the master enters the door, he practices to see the individual. Some of his theories are still readable and the crystallization of the wisdom of the older generation, but to put it bluntly, he still has to write his own code.
//Personally, I think that programming depends on editing, that is, trial and error and understanding mistakes. No book can say that it lists all the pits. Stepping on the pit is also to increase knowledge. Remember, you can read books, but you can't read more.
//Look at other people's code and keep an "inquiry" heart. What is its purpose? In order to achieve what function, does each step have its meaning? After understanding, you should "improve" rather than copy, which has no learning significance.