High quality C/C ++ programming guide

I found a good book "High Quality C/C ++ programming guide", and my information sources are not very sensitive or I have a dull sense of information, so now I can see this book, my teammates introduced me to me before, but I didn't see it. Now I can use it to regain this book.

How do I evaluate a book? First, I will read the introduction. If there is a brief description by the author, the quality of a book will directly affect the author's attitude. A good book will not come from ZB's hands, A brief description of the author can always give the author's attitude towards publishing a book. The second is to roughly browse the book catalog. What does the book teach you? Why? What to do next is your own business. So in the directory, you can extract whether the book is suitable for you, because the best book is the best for you. The plane won't fly very well. What can I do for you? Therefore, do not pursue fashion and learn for knowledge.

After talking so much about the "High Quality C/C ++ programming guide", this book is good at the combination of practical theories, he wrote his many years of summary with a modest mind. Whatever the content of the book, we can share with you all that deserves our respect. After all, the ability of a person is limited, and the author puts it bluntly: how many software developers are familiar with quality attributes such as correctness, robustness, reliability, efficiency, usability, readability (comprehensibility), scalability, reusability, compatibility, and portability? And can it be used freely in practice? This is a question worth pondering.

There is another section

I plan to define a programmer and a programmer. Don't laugh.

Definition 1: programmers who can write high-quality programs stably for a long time are known as experienced programmers.

Definition 2: programmers who can stably write difficult and high-quality programs for a long time are called programming experts.

According to the above definition, I immediately got the first inference: I am neither a master nor a veteran.

 

Here we can see how modest the author is, in fact, the author is already very good.

 

I will learn from some of his hopes:

 

(1) correct the error;

(2) learn new things frequently due to warm-up;

(3) keep learning and study every day.

 

 

I just want to talk about the author's intention to write this book. I will not comment on the quality of this book, we hope that our colleagues in various fields will do what they can for this big IT environment ·····