Revision as of 16:41, 30 November 2010 edit Mmeijeri (talk \| contribs) Extended confirmed users 5,533 edits →Which type of testing ensures that refactoring does not change the behavior of the code ← Previous edit		Revision as of 21:51, 4 February 2011 edit undo Ed Poor (talk \| contribs) Extended confirmed users, Pending changes reviewers 59,703 edits forest vs. trees, let's get with it, people! Next edit →
Line 112: In regards to the article [[Redesign (software)]], I read that this is apparently "Code refactoring" applicable to the entire software solution. Do you think that the redesign article needs to exist, since the difference between the two appears to be scale - and that would be subjective (i.e. how much code can we refactor before its considered redesign)? My opinion is that article should simply redirect here... thoughts? [[User:Jwoodger\|Jwoodger]] ([[User talk:Jwoodger\|talk]]) 00:28, 9 February 2010 (UTC) ==Can't see the forest for the trees== I want to emphasize, as someone who's done this for a living at times, that the '''refactoring process''' and '''a refactoring''' need to be distinguished. While a single "refactoring" ought not to make any changes in functionality, the purpose of doing a series of refactorings is to '''support''' changes in functionality. --[[User:Ed Poor\|Uncle Ed]] ([[User talk:Ed Poor\|talk]]) 21:51, 4 February 2011 (UTC)

Talk:Code refactoring: Difference between revisions