Revision as of 21:44, 4 January 2014 edit MadScientistX11 (talk \| contribs) Extended confirmed users 4,453 edits →Reengineering is NOT refactoring: new section ← Previous edit		Revision as of 22:09, 4 January 2014 edit undo Mmeijeri (talk \| contribs) Extended confirmed users 5,533 edits →Reengineering is NOT refactoring Next edit →
Line 151: Right now Reengineering (software) points to this article. That is an error. Refactoring is not re-engineering. Re-engineering is analyzing code in legacy environments to capture designs, business rules, and/or to automate transformation of the code into a more maintainable form. Refactoring is just a normal part of the evolution of an object-oriented systems. They are related but different concepts. --[[User:MadScientistX11\|MadScientistX11]] ([[User talk:MadScientistX11\|talk]]) 21:44, 4 January 2014 (UTC) :Sounds like the same thing to me, one is refactoring done during normal development, the other is long overdue refactoring that should have been done during development but wasn't. Refactoring simply means making tiny behaviour preserving transformations that make code easier to read and maintain. [[User:Mmeijeri\|Martijn Meijering]] ([[User talk:Mmeijeri\|talk]]) 22:09, 4 January 2014 (UTC)

Talk:Code refactoring: Difference between revisions