What is code Daquan about?

What does code Daquan (Chinese version) Version 2 mean? What programming language does she talk about? C, C ++, Java, C #, or visual basic? Are all the Code listed? Can I copy & Paste Code directly to my project?

The English name of this book is "code complete", where code is code and complete is "complete. Code complete is a period in which "after all the code is written, you can start the system test". It corresponds to "design complete.

For example, the project schedule can be written as follows:

Date target
April 3 design complete
September 30 code complete
December 10 release

Indicates that all coding work will be completed in September 30 and the system testing phase will be completed. So you 'd better not expect this to be a real "code book ":)

What is this book? Why can I get a 5-star rating on Amazon?

This book is neither an encyclopedia of software development nor a book on software engineering. There are already a lot of books on Software Engineering (many of them offer special prices :)). She doesn't talk about how to manage projects, but tells you how to use proper development tools and methods as a programmer to communicate with your boss wisely (Chapter 1: key building decisions ). She doesn't talk about how to do requirement analysis, but tells you, as a programmer, how do you determine whether the demand analysis work is in place and whether you can start the next activity (section 3.4: requirements ). She doesn't talk about architecture design, but tells you, as a programmer, how do you determine whether the architecture is well designed and whether it can support subsequent construction (Construction) (section 3.5: architecture prerequisites ). This book does not talk about system testing, but tells you how to test your code as a programmer (Chapter 1: developer testing ). If your code is rarely tested by others, your reputation will be high and everyone will trust and respect your work. Therefore, you need to test the code yourself.

So what is this book about?

This book mainly talks about construction, an encyclopedia of software construction. "Build" is the activity of converting design into code in software development, commonly known as "code ". Including how to design in detail, how to code and debug (this is the top priority), and how to conduct unit testing and integration. Of course, without the "Code Performance Optimization" technology that every programmer cares about, she teaches you how to write high-quality classes and How to Write high-quality subprograms (functions, methods, etc ). How to get meaningful names for variables, How to Write clear statements, how to format and layout code and comments, how to test developers, how to debug, and how to use assertions. These seem very detailed, but the devil is hidden in the details. The Details determine success or failure, right. From the topic point of view, it is somewhat similar to "Programming Practice", but this book is much more detailed and involves more topics. (This book has more than 800 pages, and that book has more than 200 pages .)

Is this book suitable for junior programmers? It depends on how many beginners you have in your mouth. I am afraid it is not suitable to learn the first programming language at the beginning. If you have learned a language, such as C (preferably an object-oriented language, such as C ++, Java, or C #), and want to improve programming capabilities, then it is no longer appropriate.

Is this book suitable for senior programmers? The author thinks this book is suitable for "experienced programmers" and can be used as a development manual.

Is this book suitable for project leaders? The author thinks this book is suitable for "technical leaders". He says, "many technical leaders (or technical leaders) they used code Daquan in their team to train experienced programmers." Maybe you can use her to train new people.

Is this book suitable for students? The author believes that "this is a necessary book for students who are switching from an academic environment to a professional development environment ." Let you know what qualities professional programmers need to possess.

Is this book suitable for me? If you are not sure whether you need this book, I suggest you read chapter 1 "table-driven technology" directly. I think you have mastered the table-driven technology (also known as the small language, A technology that turns code into data) is one of the important watershed for dividing junior and senior programmers.