the value of DRY has nothing to do with "typing less" - this claim is either a strawman or misunderstanding.
the point of being DRY is to gently push you to develop abstractions that fit your problem domain and allow you to centralise and locate your bugs.
lumping "similar looking" code together isn't an abstraction, it's too superficial and contextual to be useful and will result in the issues raised here... this is just going through the motions without really understanding the "why" of refactoring out repetitive code though...
high-quality abstractions are literally the only tool we have to fight nonlinear complexity growth in a codebase, keep that in mind as a counterpoint to this article
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
the value of DRY has nothing to do with "typing less" - this claim is either a strawman or misunderstanding.
the point of being DRY is to gently push you to develop abstractions that fit your problem domain and allow you to centralise and locate your bugs.
lumping "similar looking" code together isn't an abstraction, it's too superficial and contextual to be useful and will result in the issues raised here... this is just going through the motions without really understanding the "why" of refactoring out repetitive code though...
high-quality abstractions are literally the only tool we have to fight nonlinear complexity growth in a codebase, keep that in mind as a counterpoint to this article