I have heard of this book a year ago. At that time, I had just finished my research. Because of the computer-oriented research (the communication engineering of this science), I often use water forums, I have learned some classic books in this direction, and I have mentioned this book. Others' experiences in this book are "one of the books that must be read in the computer field", and "the only book that the university is willing to leave" Yun. With some doubt about others' experiences, I wrote down the name of this book-computer systems a programmer's perspective ....
It's getting longer and longer. Half a year later, I heard the recommendations of others again, but I still remember them... I asked my senior brother to recommend a few books that day, but I improved a lot in the middle. When I mentioned this book, I still remember the old brother's long sigh: "It's too classic, It's too classic... ", huh, is that exaggerated? I don't know how many versions have been printed, and how many teenagers have learned and read it. No one has said this, but a computer book has made Daniel so angry, of course, the touch on me must be an observation book.
I obtained a copy that night, read it for a week, and then shelved it. (At that time, reading in order, reading a lot of code in Chapter 2 is really annoying ). During this time (half a year later), I picked up this book again because of the project's needs. I carefully read the last three chapters and once again realized what my senior brother told me at the time-it was so classic... think of this, and summarize your reading view-reading which you are most interested in, so that you are happier, not necessarily step by step.
So far, I should not think too much about it. I want to finish the first few chapters while finishing the project. I hope that I will not give up halfway this time (I just want to collect books, not use books ), I want to write a summary after reading this book for myself and for others. Finally, I recommend again to encourage you.