2 ms·
> I content there's something quite different between e.g. removing an unused argument or renaming a variable (both of which should be entirely automated, and h
by lmm 4y ago
> I content there's something quite different between e.g. removing an unused argument or renaming a variable (both of which should be entirely automated, and hardly count as refactoring) and separation of concerns, which concerns the purpose, architecture and operation of the code.
> I heartily endorse tidy code, good naming, etc. I would put that, though, in a separate category from refactoring.
I don't see the distinction. In either case you're trying to change the code into some equivalent code that's easier to comprehend; separation of concerns may involve more subjective judgement than applying consistent formatting to your source code (though I've seen plenty of subjective arguments about the right way to format code), but they're both the same kind of work.
> "Access to source code" is a maintenance goal, it just usually goes without saying and is rarely an issue.
I've never seen it considered a "goal" for any usual definition of goal. Rather keeping access to the source code is something you do as a means to an end; you want to make sure you can easily achieve future maintenance goals, even if you don't yet know what those goals are. And I'd take the view that refactoring to make your code more easily comprehensible is valuable in the same way and for the same reasons.