It’s pretty obvious how WET code (We Enjoy Typing or Write Everything Twice) breeds defects: developers modify one instance of the duplicated code block and
Tag: DRY Principle
Negligible performance penalty for calling a function vs. accessing a property.
In the last post, I offered this little object as a way of encapsulating a get() / set() pair and their backing variable. function Variable(initialValue)
A property with a backing variable is not DRY.
Believe it or not, I’m still not done with DRY Principle (Don’t Repeat Yourself). This short post is about a non-DRY practice that is so
The Builder Pattern keeps your code DRY.
Last time, I went on a little rant against object literals, laying out a case that they are enemies of the DRY (Don’t Repeat Yourself)
Object literals are enemies of the DRY Principle.
In the last post, I explored three ways that the DRY Principle (Don’t Repeat Yourself) means more than just “don’t repeat blocks of code.” In
The DRY Principle is more than avoiding duplicate code.
The craft of software engineering has changed a great deal in the last couple of decades, but Hunt & Thomas’s advice from 1999 is timeless: