Read code Daquan

Some time ago 《CodeThe book goes down on the Internet and saves the cost of books. Of course, this is wrong, from the perspective of copyright or eye care. The English version is named "code complete". From the perspective of the book content, I prefer to translate the book name into "code writing guide". This is indeed a book on strategy and best practices.Chapter 1 describes the "metaphor" in software development ". Software development is a relatively new activity. It is easier and more profound to understand software development through existing activities. The author most agrees with the metaphor of "building software". The following is a metaphor for go.

In software development, a lot of work requires rigorous logic thinking-such as writing a childProgram, WriteAlgorithm(Equivalent to local computing in go), while design requires divergent thinking, such as determining the direction and strategy of the game in go. "Design is a sinister problem", while the strategic decision-making in go is also full of variables. "design is a non-Chapter process ", however, there is no rule in the strategic decision-making in go, which can be found by any of those great ideas. "Design is uncertain." different strategic decisions in go are often difficult to distinguish between advantages and disadvantages.

programmers with" Pragmatism "may think that the" best practices "of" academic "programmers are one more action; I think there are no disadvantages to some best practices-because in code, there is no conflict between beauty and practicality. The elegant code is concise and clear, and its value will be reflected in the maintenance and expansion in the future. The "Bad taste" code is a potential trouble maker. The word "taste" is also used in GO games. A good game is as quiet as a child, and its potential is hidden. A bad game is a burden of playing games.