I usually read a book three times.
First time
Read-through, without understanding, but for speed, after a few days, you will be familiar with the content and structure of the book.
Second time
Slow reading and close reading. With the foundation of the first time, you can arrange to read the part you are interested in based on your own knowledge and experience. Finally, let's take a look at the part that you are not very interested in.
Third time
When will it suddenly become unclear?
I spent a week in my spare time reading this book. I deeply understand Python and have a profound knowledge. I just want to explain the internal mechanism of Python, the content is reasonably arranged, and the difficulty level is also appropriate
The Python bytecode explained in the book reminds me of the machine language and the machine architecture. The language development started with assembly, and many types appeared before and after. It should be said that the popularity of C marks the beginning of a new programming world. Using C can be a lot different from machines, of course not all. Then this is enough to greatly improve the programmer's ability, the progress of history is the progress of ideas and tools. The popularity of C proves that the process-oriented thinking is excellent, the development of compilers, and the standardization of syntaxes consolidate the world of C.
A person has a property. Everyone has a "Laziness ".
Looking back, C has no class, no namespace, and no module. Of course, these can be implemented in a different way (such as objectc), but this is not in line with the lazy habits, therefore, more intelligent and efficient languages are emerging. The Class C ++ came into being, and in order to show itself how powerful it is, it turned out to be a template and a paradigm programming. Cross-platform Java, step-type python, PHP, Perl, Ruby...