Re:Prefer duplication over the wrong abstraction
by weberc2 on Saturday July 09, 2016 @01:19PM
(#12062323)
> Why would deduplication stop maintenance?
I didn't say it would, I said it would stop repetitive maintenance--meaning you won't have to update many duplicates of the same logic because there aren't duplicates.
I tried to update my comment to be more clear, but I'm not sure that I succeeded. :p
Why would deduplication stop maintenance? Unexpected NullPointerExceptions are found. Unexpected UTF-8 string inputs are discovered. An interger overflow is discovered. A memory leak is found in the method. The method is used in a performance critical loop and now must be optimized.
Maintaining code is the majority of programming work that I've witnessed. If multiple copy/paste methods have to be maintained, it always devolves into a mess of technical debt until someone comes along, pays the debt, and pulls them all up into the same abstraction.