Today, I occasionally visited the Martin Fowler's Blog, I saw an article entitled "refactoring malapropism" in his Blog. It is to talk about "refactoring", and also discuss the definition problem of "refactoring". Very shallow, but I feel very reasonable. I think that its article is to clarify the difference between refactoring and restructureuring.
Refactoring for a built-in system within a while is a refactoring, the so-called refactoring of the document cannot be called Refactoring, but should be referred to as RESTRUCTURING.
The general sense of restructuring represents "Any RearRangement of Parts of a whole"; Refactoring belongs to special technology, specific RESTRUCTURING, which uses a small behavior of behavioral maintenance.
Combined with Martin Fowler's definition of refactoring in its "Refactoring" book, the above view is not difficult to understand. It seems that Master is still very stubborn in this regard :)
BTW: There May BE Other Good Techniques for Restructuring, But They Are Different - There are other restructuring technologies, this is a very curious thing.
Http://martinfowler.com/bliki/refactoringmalapropism.html
