Re:How to Become a Bad Developer
by cactus2093 on Thursday June 17, 2021 @02:12PM
(#27542597)
> to ask whether a future change in the logic to one would imply that a change should also made to the other.
If there's a really obvious answer to that question, then great. But often the answer is "sometimes" or even "most of the time". We train most developers beginning even in intro-level programming classes to err on the side of deduplication and over-abstracting in these cases, but the longer I've been working as a developer the more I have come to think it's better to err on the side of allowing some duplication except in the most clear cut of cases.
Re:How to Become a Bad Developer
by Wowfunhappy on Thursday June 17, 2021 @12:23PM
(#27541389)
What if a change to one would imply a change to the other, but also the block of code is needed in 20 places instead of two?
If so, then by keeping them separate, you introduce the risk that you would forget to update the other. Using a single function and calling it twice, even with different parameters, is a way communicating that it's important that the semantics be tied.
If a change in one wouldn't imply a change in the other, then you really have two separate semantic roles being played that happened to resemble each other in implementation - harmless incidental duplication.