Revision as of 01:35, 25 January 2008 edit FrankTobia (talk \| contribs) Extended confirmed users 4,318 edits →Software Methodology: response ← Previous edit		Revision as of 13:00, 12 March 2009 edit undo JulesH (talk \| contribs) Extended confirmed users 5,584 edits →Refactoring to improve performance?: new section Next edit →
Line 82: :::Haha, fair enough. I'm happy to keep you honest. Of course anything with a source would be amazing: I don't have access to those most excellent refactoring books myself. Let me know on my talk page if there are any related pages I should add to my watch list. -[[User:FrankTobia\|FrankTobia]] ([[User talk:FrankTobia\|talk]]) 01:35, 25 January 2008 (UTC) == Refactoring to improve performance? == Including this seems a little controversial to me. Performance is not a "non-functional" aspect of a system's behaviour. And while some refactorings clearly improve performance, and some techniques to improve performance are clearly refactorings, I think performance optimization is a distinct process. And as Fowler says in ''Refactoring'': :Only changes made to make the software easier to understand are refactorings. A good contrast is performance optimization. Like refactoring, performance optimization does not usually change the behavior of a component (other than its speed); it only alters the internal structure. However the purpose is different. I'm going to remove improving performance from the list of reasons to refactor. [[User:JulesH\|JulesH]] ([[User talk:JulesH\|talk]]) 13:00, 12 March 2009 (UTC)

Talk:Code refactoring: Difference between revisions