DRY is more about support and maintenance than anything else.
I see a lot of attacks on DRY these days, and it boggles my mind. Maybe it is being conflated with over-engineering/paramterization/architecting. I don't know.
But I do know that having to fix the same bug twice in the same code base is not a good look.
I see a lot of attacks on DRY these days, and it boggles my mind. Maybe it is being conflated with over-engineering/paramterization/architecting. I don't know.
But I do know that having to fix the same bug twice in the same code base is not a good look.