Thinking about Some Problems in code book 2

CodeDaquan is a very good book, but it is not necessary for many developers to carefully read this book. Check whether the content of the table in the book is clear. not necessarily. I want to write some experiences or questions about this book, hoping to help other developers.

1. read this book.

This book is a classic, needless to say, whether it is code Daquan 1 or 2, it shows its content as a classic. however, one reading cannot obtain the essence. my requirements for my subordinates are as follows:

A: First, you must read it repeatedly. It is not enough to read it three times before you can get a preliminary understanding of the situation.

B: Reading is for understanding. Many people do not want to write comments in the book, but I think it is necessary to keep writing comments when reading this book, this book leaves a lot of space for you to write comments. Why not?

C: I need to use my mind to read books. I should keep thinking about this book. For example, whether the viewpoint in the book is correct or not meets the requirements of the book in the previous development process, what is the effect? What is the original problem? It is because it does not follow a rule in the book, and what is the harm. These things can only benefit from repeated thinking.

D: You can write your experience in a book every time you re-read it. Don't be afraid that you may not write it wrong. Read it once every time you finish developing a project and write your own experience. The effect is remarkable after repeated attempts.

In the future, I will not write my own experiences. I hope to share with you the fun of Development and reading.