Before reading a book I used to read the preface and introduction, in which this sentence makes me feel a very deep person. "If I were managing a project, author of the book is what I want .... .. If you can not, I'll want to read the books of them, "I think this is what I need, and I am determined to make myself read and read a good book determination on the bed, moments read.
"Pragmatic Programmer" by a series of independent parts, about the many entertaining anecdotes, thoughtful examples, and interesting analogies. After reading part, I feel this book compared to the first reading of the "Road to Jane" is more easy to understand, the basis of which the comparison was talking about, not the kind of large-scale programming, high concurrency design, etc. , mainly to do some basic qualities for programmers and some basic common programming design and specifications of some sort, which is very important for us, I think this is some of the essential qualities of a qualified programmer should, in addition to content design outside of this book also has a very characteristic One of my favorite and most attention in the book given in the prompt box, simple but profound meaning.
After reading the first chapter (pragmatic philosophy) and Chapter II (pay attention to the effectiveness of the way), I really gain a lot, even if it is in programming ideas, some programmers or programming practice professional quality needs, I have is a benefit. School is also very practical, for example, in the book there is a word it says " the Do not Live with Broken Windows", this sentence gave me the programming idea is that when your program has encountered a little problem can not be easily give up, should combine their own knowledge, and access to relevant information, research concentrate on it, and reach into your learning from this process, to expand their knowledge. It also requires a lot of us try to train and master a variety of questions, and have the habit of writing your own code, after long-term accumulation to form their own code base. But if full account of the work, we should expect to do error handling that may occur, a balance between accuracy and robustness of programmers; we should have as a programmer and different tests for different software Note focus, such as personal safety-critical software more inclined correctness, we should focus on consumer applications software robustness.
In the process of writing code, the code will encounter many problems, beginning with the source code I let the cat to eat, talking to shoulder their responsibility for their own code, middleware and some errors to be immediately resolved, or will becoming larger and larger, leading to irreparable mistake last, there is a stone with boiled frog story, let them do the procedure to foresee the future, think of ways to raise resources they need. In short, this book is helpful to me, I will continue to read on.