Re:The High-Risk Refactoring
by seadan83 on Tuesday March 19, 2024 @11:18AM
(#39756645)
Our industry suffers from terms becoming popular and then losing their meaning. By the current meaning of refactoring, it can mean anything from a 2 year redesign of the full system to simply extracting a boolean expression to a variable. From Martin Fowler's definition, refactoring should not be so large, "Refactoring isn't a special task that would show up in a project plan."(https://refactoring.com/)
Personally, I would tend to draw the distinction between tactical refactor and strategic redesign. Even the "main" organization of the code could fall into the refactor camp for me. Something I would think of as very clearly re-architecture would be a transition from a trigger based system to an event driven system.
Personally, I would tend to draw the distinction between tactical refactor and strategic redesign. Even the "main" organization of the code could fall into the refactor camp for me. Something I would think of as very clearly re-architecture would be a transition from a trigger based system to an event driven system.