Timeline for How can I make refactoring a priority for my team?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2024 at 15:04 | comment | added | Divan | This is what a lot of developers don't realize. Your boss will probably never give you time to refactor. You have to make time by making refactoring part of your daily work. Usually as part of bug fixes or new features. | |
| Aug 24, 2012 at 10:13 | history | made wiki | Post Made Community Wiki by Stefan | ||
| Aug 14, 2012 at 11:16 | comment | added | Joeri Sebrechts | I've seen the kind of "this needs to be refactored" comments sneak in on code that is reused in other places but where it's not very clear which ones those are. Usually the developer doesn't want to spend the time to do impact analysis, and they put in the comment to assuage their guilt. | |
| Jul 13, 2011 at 8:38 | comment | added | Maxpm | @Thorbjørn I'd say you should have a good idea of where the function is being used. If the given source file is being compiled for something internal, i.e. so you have complete access to all its callers, I don't see a problem with fixing it and updating the places where it's called as needed. If the source file is being compiled as part of a library where the API can't be changed, you could at least fix implementation details. | |
| May 18, 2011 at 17:42 | comment | added | user1249 | if you just happen to pass by a function which can be improved a bit. You just don't know that it is placed in a common library? | |
| May 17, 2011 at 21:42 | comment | added | Karl Bielefeldt | Good point, @Thorbjørn. Something like that I probably wouldn't classify as a "small" improvement because it has a large scope of influence. | |
| May 17, 2011 at 21:01 | comment | added | user1249 | Strongly depends on how close you are to a deadline. Changing a library may invalidate all previous testing. | |
| May 17, 2011 at 20:34 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |