If you are getting many defects due to fallout from unrelated changes, it may be a sign that your code does not follow the Single Responsibility Principle!
This post is a mea culpa. I’ve always believed that a software team must be led by someone who still knows how to code and
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
I love programming, but even if I didn’t, I couldn’t give it up because I would feel like I had failed at my life’s quest,
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
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)