Classic software books

Valid C ++: 55 Specific Ways to Improve Your Programs and Designs
More Effective tive C ++: 35 New Ways to Improve Your Programs and Designs

For example, if you want to be a qualified C ++ programmer, there are many classic books to recommend. However, if you want to be an efficient C ++ programmer, you must never miss Scott Meyers's famous books. Meyer has almost set off a wave of disruptive programming. For example, the subsequent disruptive STL and the alternative C #, which inherits the same style of Bill Wagner, are among the best in this series. People relish the terms in the book, apply them to programming practices, and are deeply impressed by Meyer's technical conservation. The reality is exactly like this. Using C ++ to develop a project is like moving through a minefield, warehouse, and the idea of hitting the game, so be careful, this means that you are not ready to take the lead. These two books by Meyer are detectors that help us navigate through the minefield. They can remind us to avoid dangerous mines and even help us remove mines so that we can pass through safely and reach the destination of victory.

I often read these two books when writing C ++ code. I cannot hide them. Whenever I encounter a C ++ trap and cannot extricate myself, I need to find a powerful tool to solve the problem from the book. This is a must-have book for C ++ programmers. Even for Java and. NET programmers, reading these two books is still beneficial. GC can help us avoid many memory traps and avoid system crashes due to memory leaks. However, from an efficient perspective, no matter what language, there are similarities, the topics in the book can be said to be a universal language. For example, in Objective C ++, in-depth analysis of design, implementation, object-oriented, and many other concepts; in More objective C ++, polymorphism, exceptions, efficiency, and other miscellaneous discussions can be fully isolated from the specific C ++ language and benefited from the general programming perspective.

The so-called "classic" means that it will not lose its value because of the passage of time. Language changes have been overwhelming for decades, but the charm of C ++ remains intact. I think even if C ++ goes to the end in the future, these two books will not be outdated, and they will continue to develop powerful vitality, because, it captures the essence of software design and development.

Pragmatic Programmer: From Journeyman to Master

Ward cunnhan said: "If I am managing a project, the author of this book is the one I want ...... If I cannot, I will ask someone who has read their books ." Such praise seems exaggerated at the beginning, but it is appropriate to think carefully, because the book has only one argument to prove over and over again, that is, the philosophy of focusing on effectiveness. Our industry requires effective programmers.

I did not read this book to get cunnhan's employment, nor did I rush to publicize it from small workers to experts. I read it because it is worth reading; I recommend it because it is worth recommending. This book has received a lot of praise. Kent Beck, Martin Fowler, Kevin Ruland ...... They are masters of the industry. Isn't their recommendations enough? Standing in front of them, I am just a small engineer. But don't forget that the readers in this book are not experts, masters, or ordinary programmers.

Do you remember stone soup? Do you remember window breaking theory? Has the source code been eaten by cats? This is a feature of books by Andrew Hunt and David Thomas. Vivid, lively, simple, and concise, but careful meditation, these metaphor all contain the meaning of permanent, impressive, can be used as a rumor or motto of programming.

This book is not just an exquisite metaphor. Hunt and Thomas sell neither literary theories nor gorgeous philosophies, but programming. If Martin Fowler's refactoring is a battle against the bad taste of code, this book is to declare war on the old and bad habits of coding. It has both strategic thoughts and decisions, as well as tactical skills and tactics. On the whole, it provides the programmer's practice rules, and you will have the opportunity to become an expert to follow these rules. This book covers all aspects of programming and project management-how to temper time-tested code, how to start effective development, how to solve ugly repetition and rigidity, how to overcome the arrogance and prejudice of cooperation, how to improve the efficiency and quality of algorithms, and how to build code that is easy to test ......

The dream of becoming an expert is floating in the distance, and this book will become your sight. All right, aim, shot, target, red-hearted!

Art of UNIX Programming

Unix is a fun scene for Geek, where there are veteran hackers and cutting-edge fighters, senior scientists, and weird hacker groups. They are here with their talents and enjoy the golden youth. This is Eric S. Raymond's loose poems in this happy world, such as the vicissitudes, immortality, and strangeness of the homic. The reason for this is that the content in Chapter 2 of this book is a review of the origins and Historical Changes of Unix in an epic style.

Many readers are easily confused by the title of this book, and think that this is a big blog encyclopedia about Unix kernel and development. If you think this way, you may lose an important mentor and friend. Especially for developers in Windows operating systems, do not reject it because of Unix, or stay away from it. The art of programming has no operating system limitations.

Well, let's first look at the Unix philosophy given in this book. For example, the simple interface is used to combine simple components, clear is better than clever, the policy is separated from the mechanism, the design is concise, and robust is derived from transparency and conciseness ...... Is this about Unix? Raymond seems to be drunk!

Let's take a look at the second and third parts of this book. Encapsulation and optimum module size, compact and orthogonal, Unix interface design pattern, complexity and reuse: Don't re-invent the wheel ...... Well, we can conclude that Radmond is nothing more than a fake Unix name to spread the art of design to the audience. He is a evangelist of Unix culture and a pioneer and mentor of elegant design. I don't know anything about Unix, but I 'd rather spend 1/2 of my free time reading this book until I have burned the symbols of Unix culture. My experience is to complete the reading of this book, which is actually a pilgrimage towards Jerusalem. My admiration is not for Art of UNIX Programming, but for Eric S. Raymond, but for Unix, one of the greatest works in the 20th century.