Refactoring the Dimension - Reconstruction and "Reconstruct"
I rarely participate in my books, because such comments will lose fair and strange feelings at the same time, and both are the elements of excellent books. I also have the same embarrassment for this upcoming "reconstruction". What else do I want to find before looking for "Reconstruction Letters" Since there is no comment, I invite readers to share these messy thoughts. I have repeatedly talked with my friends many times, translation is an interesting job, and translation is an irresponsible attitude. The term "reconstruction" is one of the words of extensive misunderstanding and abuse in this "interesting work". I saw this word in the impression and is in Habermas's work. The word "Nachkonstruktion" (post-structure) "," Nachkonstruktion "(post-structure), and unavoidable" Reconstruction "- reconstructed in translation into English. This is a vocabulary of a particular research behavior, which is quickly abused by China's cultural people. After entering the 1990s, in the exclusive sound of industrialization, "modernization", in the enthusiasm of the spirit of Renaissance, a large string shifted in the industry: Re-Organize, RE-STRUCTURE, RE-ENGINEER, RE-Design ... It is quite interesting that these obvious words with Wall Street smell are mostly translated as "reconstruction" when used alone. Maybe it is to borrow Philosophical circles? Since Alexander, some people often share the software and architectural ratios. Unfortunately, software theorists have not learned something else, and they have learned "modernity" - structuralism. When the "software engineering" is keen on the management of the department, when the perfect design structure is pursuing the perfect design structure, we can only celebrate the cruelty of the shopping mall to make them no chance to continue their own try. When the structure of the structural trial is in trouble, the discourse-constructed words immediately: Rad and "Good Enough" think about it makes people feel that it is an uncomfortable labor. From the 1980s to the 1990s, the CRACK-style software development and personal hero's programmer finally left large businesses and large hosts, and the legendary legend was as tempting as the western story (and the same illusory) . Direct promoting this post-modern wave is undoubtedly the emergence of PC and a series of achievements of Microsoft, and the Share Software's Golden Dream needs to be responsible for the programmer's quick drop in the excessive deconstruction direction. Fortunately, this situation has not been maintained too long. Java brings more than just a new language and a new platform, as well as regression and reconstruction of the SPS software structureism. The grammar in which C-pulse is inserted, as well as the language from SmallTalk, making Java a value of value reconstruction. At this point, our "Refactoring" has floated in the Java community, which is not surprising. Whether it is a German philosopher 's REENGINSTRUKTION, or the reengineering with American entrepreneurs, with a "destructive"-reconstruction after comprehensive deconstruction, which is a commonly used routine for postmodernist. Wolfgang Well Shi's undoing AESThetics is also translated as "reconstruction aesthetics", and it is true that "reconstruction" is indeed "overthrowing an old world". However, the refactoring in "Reconstruction" did not destructive. In fact, the first element of Refactoring is the semantic maintenance, and then consider improving the inner structure without changing the program's observational behavior. Therefore, although it is also translated into "reconstruction", refactoring is a more conservative, more cautious process. For the word "reconstruction", it is more important to "construct".
When you refactor, what are you building? I have two directions: Martin Fowler said that you build a self-description program, you can let the reader do not need to understand the code that can be understood by the document; Joshua Kerievsky said, you build design mode (Design Patterns) ), Is an elegant design that gets over-engineering. In my opinion, reconstruction requires programmers to build a sense of responsibility, for the code, for colleagues, responsibility for the occupation, which is something that software engineering and Rad are ignored. I remember that there is a book review putting this Refactoring with Design Patterns, Anti-patterns, and Extreme Programming Explained as the Bible of the Java Industry. For this commentator, even if you don't learn anything, I will at least think that he is ignorant (four "Bibles" have two from Martin Fowler's only counsel). Perhaps there is a personal emotional factor, I hate the "reconstruction" as a classic. When promoting a technical means to keep, progressive development, "Reconstruction" is unwilling to give it the reader's 醍醐 顶 顶, but is more happy to let the readers live the lifestyle of "eating clothes is human physics". Yes, in my opinion, reconstructing more is a lifestyle, maybe just like the programmer, it is the same as that of the code. And the classic, that is a word alpine, I am afraid it will give readers to prepare the next wrong reading mentality. Since the refactor is a technique that pays attention to maintaining the status quo, I also hope that the reader should not change the earth by this book. Unfortunately, Martin Fowler wrote this book, he can only tell readers JUnit, manual reconstruction, and the legendary refactoring browser. In order to make up for this point of defect, I will first download an Eclipse, learn to use Junit, learn how simple reconstruction has been provided (starting with the most common EXTRACT METHOD), then open this "heavy "- In addition, always keep in mind lazy is a virtue of programmers, don't recover your code because I am excited. "Reconstruction" is a book: Maybe you will not read the second time after reading it, but you will always think of it, because it has subjected to your habits. If you feel "I have learned to be refactored" after reading it, I am sorry that you have not learned anything. At this time, maybe you should make you calm down and want to "reconstruct" the word "Reconstruction", try again to do a little restructuring in your own code. Until one day, you have already forgotten this book, but it is already reimbursed to your code at any time. At that time, you are really "learning" - but you are already unreasonable. This is a moment of "reconstructed" in the imagination, and some of my mind flashed. Will this abrupt text help you help? I don't know, I am just telling myself. So where is the evaluation of this book? It is only in you. only the guy drinking water knows it's cold or hot. What is "reconstructed"?
More than once, I heard the masters in our industry (at least) quote for reconstruction technology: "That is what we have been doing in the past fifteen", "I (last century) 70s I have already begun to do this, "" The hackers on UNIX have been doing this "... these speech makes me very interesting to explore the exact." In this "reconstruction", what did Martin Fowler give his readers? "Reconstruction", is it to reveal the gospel book of the new era, or call the advertising word for soup? Reconstruction (noun): An adjustment of the internal structure of the software is to improve its understandable and reduce its modification without changing the behavior of the software. Reconstruction (verbs): Use a series of reconstruction actions to adjust its structure without changing the operation of the software. This is a good definition that is a bit of a bit. Reconstruction, that is, such a kind of plenty of technology - or set up in front of me, lifestyle. Like most old programs of C and C , Eric Raymond's first reaction when reading this "Reconstruction" is: "Hey, the young man is not on the side of the code side. We manage this called ' Hacking '! "Nature, successfully ensembled, his second reaction is:" Martin, this guy, installing him, I don't know how to be,' Hacking 'is so stupid. Is it true still stupid? "Please allow me." Temporarily interrupt the thoughts of ERIC (or you, my readers). Unlike China's universities, the Ph.D. in the University of Illinois is not so easy to get it, especially when your mentor is Ralph Johnson. William OpdyKe laid the theoretical basis for the retroactive technology in his doctoral thesis, and the core of this doctoral thesis is the study of "behavior maintenance". Briefly, in this paper, William has proved by mathematical methods that the program modification of the program will not affect the behavior of the program (ie "behavior holding"), and the behavior is maintained in the case of satisfying specific conditions. The combination between modifications will continue to be a behavior. So, from the first day of the birth, the feet of reconstruction techniques firmly stood in the arms of the earth. Eric raymond's spokesperson becomes free software, a large extent, a sharply keen technical sense of smell. His third reaction is: "Hey, these things in Martin are indeed better than the hackers' way." Hacker culture is always lacking theoretist. Of course, there are several "theory" hackers who focus on ways to learn, such as Richard Stallman, Larry Wall, and our Eric. However, hackers almost always pass the most important experience through otters, and they are not arguing. The Martin Fowler's refactoring technology is based on the complete theoretical basis, and has a perfect methodological guidance (including the practice of "agile alliance" advocated by Xiao Tiee, frequent construction, test priority), which makes it not It is completely dependent on programmers' talents. The values of hackers are "You are a stupid, so you don't have hacking", and the reconstructed values are "if you don't go to learn, you are really a stupid" - compared with it, where do you prefer? One? The hackers are familiar with the reconstruction and agile methods. Similar to Hacking, the reconstructed cultural emphasis is important than process and tools, software products are more important than documentation, and the collaboration with customers is focusing on negotiations for contracts, and positive response is focused on following existing plans.
