Why DRY is the most over-rated programming principle
-
DRY was the first programming principle I encountered and probably the only one I was aware of for the first year that I was a developer.
It's all wet?
-
DRY was the first programming principle I encountered and probably the only one I was aware of for the first year that I was a developer.
It's all wet?
He's wrong. Simple =/= quick. It also doesn't mean less complicated. I spent years cleaning up the mess that he would have encouraged and it was not fun. Maintainability is as important as anything else and he is completely ignoring this. The art is learning when to apply things and not to apply them; not spaz out and write an article decrying DRY only to admit at the end to not toss it completely. I also smell a common issue... No RDBMS skills to allow application logic to be enforced or guided by data structures.
-
He's wrong. Simple =/= quick. It also doesn't mean less complicated. I spent years cleaning up the mess that he would have encouraged and it was not fun. Maintainability is as important as anything else and he is completely ignoring this. The art is learning when to apply things and not to apply them; not spaz out and write an article decrying DRY only to admit at the end to not toss it completely. I also smell a common issue... No RDBMS skills to allow application logic to be enforced or guided by data structures.
frontlinegeek wrote:
The art is learning when to apply things and not to apply them; not spaz out and write an article decrying DRY only to admit at the end to not toss it completely.
"There is always a well-known solution to every human problem—neat, plausible, and wrong."
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius