"Code Encyclopedia" post-Reading notes

　Yesterday finally finished this tome, the text of the book a total of 862 pages, plus the preface and the appendix has nearly 1000 pages of appearance, to tell the truth, although the book is very thick, but it looks very easy, and do not feel boring. I believe that as long as you start reading this book, you will be attracted to the content of the book and guide you to continue to look.

Using a simple counting technique to make the parentheses symmetrical, this method has been used since it was seen in the book, so I'll introduce you here: if you don't know if you're using a pair of parentheses, the following simple counting technique will be useful to start with, say "0," and then scan the expression from left to right. Say "1" when you encounter an opening parenthesis, and add 1 to the number each time you encounter an opening parenthesis. Subtract this number by 1 each time you encounter a closing parenthesis. If the result at the end of the expression is 0, then the parentheses you use are paired.

Java Example: paired parentheses

Java Example: paired parentheses if ((a < b) = = (c ==d) && ! Done) ...   | | |       |    |      |  |           | 0  1 2 3       2    3      2  1           0

In the Book of Code Daquan, the author mentions hundreds of books (or articles) of software development, and finally, the author gives a list of recommendations that we take a look at:

information about the software build:　　

　　The author's original reason for writing the book was that there was not yet a thorough discussion of the software-building book. Since the release of the first edition, there are some good books on the market.

Pragmatic Programmer (pragmatic programmer) (Hunt and Thomas 2000) focuses on the use of activities, testing, debugging, and assertions that are closely related to coding.

"Programming Pearls", 2d ed Jon Bentley discusses the art and science of software design in the context of small programs, consisting of a number of short essays.

"Extreme Programming Explained:embrace Change" Kent Beck, a construction-centric approach to software development.

"Writing Solid Code-microsoft's techniques for developing bug-free C software" Steve Maguire is a more specialized book. Production practices that focus on commercial-grade applications are largely based on the expertise of the author in developing Office software.

"The practice of programming" Brian Kernighan and Rob Pike co-authored. Another, more specialized book, focuses on the nature and practice of programming.

Programmers at work, Susan Lammers, has a record of interviews with the industry's top programmers.

outside the building of the topic　

　　The following books give a general description of software development from various angles.

"Facts and fallacies of software Engineering" Robert L. Glass introduces the rules and precepts of traditional software development.

"Professional Software Development", the author's own, discussed the current situation in the field of software development.

"Swebok:guide to the software Engineering Body of Knowledge" Abran, detailed analysis of software engineering knowledge.

The Psychology of program development

The Myth of man and Month

"Software Creativity" (Glass 1995)

"People's Pieces"

The last four, I think we have heard of, and its popularity will not be introduced in detail.

Software Engineering Overview

"Software Engineering:a Practitioner's approach", 6th ed, Roger S. Pressman, properly handled software requirements/design/quality verification/and management aspects.

"Software Engineering" 6th edition (Sommerville 2000).

About the code of the great book content, it is not here to introduce, recommend everyone to see, after all, 900 pages of books is not a blog can be summed up.

　　

　　

"Code Encyclopedia" post-Reading notes