re: What "accepted truth" in software development do you find questionable? VIEW POST


This isn't so much of a "truth" as it is an oddity.

DRYness is good. Decoupling is good. But the only way to increase DRYness is to increase coupling.


Recently I've tested making "util" classes/files (depending on language), where I put functions that have to be used from multiple classes.

These I try to keep as small and generic as possible, so that coupling errors don't happen (and so far they haven't).


Haha! 40 Classes to do one thing!

code of conduct - report abuse