Note: Mr. Robert C. Martin is a world-class master in a software development field, and is one of my favorite technical writers. His article can always refer to the problem, give the most effective, most practical, and most appropriate solution. His website at www.objectmentor.com is my favorite, articles must be read, and each one can give me a feeling of Mouton. I will know that uncle Bob will write a book about agile development, I have been paying attention to this book, I look forward to this day, because I know this uncle bob must say some things. Therefore, this book is published, I bought a friend on Amazon. Sure enough, this book tells what it is really special, saying that it gives me a kind of 醍醐 醍醐 top, the feeling of moving the cloud is not exaggerated, it shows me a complete software development "live" image .... .. I have a lot of research and practice in software development, and this book will definitely be shocking on software practitioners. It is really happy to be very happy to be able to share this must be a classic masterpiece. I hope everyone can like it.
The essence of software development - "agile software development: principle, mode and practice"
Deng Hui
There is a lot of books on software development, there is a process method, and there is best practices, and there is design principles. But when you truly software development practice, you will find that these books tell your knowledge to always have a certain gap when you actually use it. I have a deep understanding in this regard. After a period of reflection, I vaguely feel that there is still a certain thing existing in the process method, best practice, and design principles to combine them to truly play their biggest utility. This thing is not a formal strip box, but a way of thinking in the human brain. After reading Robert C. Martin, I have a sudden feeling that I have a sudden feeling of "agile software development: principle, pattern and practice" This book will clearly describe this thinking method.
This book has two major features. First, many books that describe software development are either only involved in process methods, or only involve design principles. These practices are one-sided relative to the entire software development activity. In fact, process methods, design principles, and best practices are an inextricable whole. Isolate to use any part of any part you can't get the best results. The most effective way should find a method of combining these three and supporting them in accordance with the actual situation of our own development team. For example, everyone knows that every week (day) is a widely recognized best practical method, but it is not necessary to build a week (day), it can get a good effect, sometimes, the result may Worse. To make this approach, you need other support. The premise of weekly (day) is the software must be built per week (day). That is, you need to manage the dependencies in the software so that it has the basis for the construction of weekly (day). The management of this dependency is to guide and metrics for design principles. This is just one of the examples, which reflects the author's leading ideas and practices everywhere. If the reader can experience in this regard, it will definitely have a more comprehensive and in-depth understanding of software development, so that these process methods, design principles, and best practices can be used more effectively.
Second, the core of this book is software design, but it is very special for the understanding of software design and the way. Many books on software design, either tell some of the design principles, patterns, and then give a few simple applications; either you take a final design results, then tell you how much they are. beautiful. At that time, you may really think so, but when you try to apply in your actual development, you will always find that the situation is totally different. At this point, you are either a handless, or you will misuse the design principle, mode. The reason is mainly because it is not true design in such books, just part of the design, and ignores the most important aspects of the design. The design is a dynamic activity of human thinking, which is the process of thinking, weighing, folding, and choice for designers. There will be many problems that don't have problems in ideal, and the level of processing of these issues is the real design level. Similarly, this is a thinking process everywhere. For each case, the author will think with you, discuss together, wear together, verify together. This book is shown in a complete design activity process. Through these cases, I believe that readers will definitely have a more profound understanding of the design. In addition, this book also tells a lot of design patterns, but there are many other books that describe the models, it is more, when do you tell you how to use the model, to resist the temptation of the mode, so as not to bring The necessary complexity. Today, this book is undoubtedly a more reasonable and effectively used mode. In fact, these contents are the most essential in software development activities, and it is also the most difficult to ponder. It is very difficult to express these content through text, which is why this is the reason why this is a book of phoenix. However, in this book, Mr. Rober C. Martin can write these content so clear, so easy to understand, fully demonstrate the author's deep technical skills and excellent expression skills. Therefore, this book can stand out from many outstanding books, and there is nothing unexpected.
This book mainly includes 4 parts, these contents are very important for today's software engineers, they are: Agile method: Mainly telling how to use the Agile method, which is a large part of the content is to tell you why do this. Object-oriented design principles: This book contains 11 object-oriented design principles covering the design and class of the package. This is the clearest, thorough, and delegated one book I have ever seen. Design mode: This book tells 23 design patterns, and there are specific examples. The focus of explanation uses how the most appropriate mode is selected according to the context and binding power of the current problem, and when to avoid the mode. UML: This book is not about UML, but in order to make readers better understand the content, the author uses some UML map to display design ideas. At the same time, this book also has an in-depth setup of how to effectively use UML. There are two appendices in this book specializing in UML.
In short, this book is written to the first line of software engineers. If you want to learn UML, if you want to learn how to design the software, if you want to learn design mode, if you want to learn the best software development practice, please read this book.
Thanks to Robert C. Martin wrote such a so good work, this book will be a classic. I have learned a lot from this book. I believe this book will not be disappointed.
Deng Hui 2003.8.7 in Shanghai
