> It's probably a better idea to spend your time helping to complete
> the previous refactor instead of starting your new one
That is a fair suggestion - when practicable. Often, it isn't, because of the very reasons which made the old refactor stall in the first place, e.g.:
* The target factor of the code was not such a good choice to begin with.
* The code in question is critical and any change to it is discouraged or feared.
* The code in question is the responsibility of different groups of developers / different departments, and they, or their managers, are not in the mood for collaboration.
> the previous refactor instead of starting your new one
That is a fair suggestion - when practicable. Often, it isn't, because of the very reasons which made the old refactor stall in the first place, e.g.:
* The target factor of the code was not such a good choice to begin with.
* The code in question is critical and any change to it is discouraged or feared.
* The code in question is the responsibility of different groups of developers / different departments, and they, or their managers, are not in the mood for collaboration.
etc.