You're completely right Amy, fast and quick solutions that does not seek the root causes, or deep needs of the code, does not work. Some things cannot be fixed overnight.

I realize now that my article was pretty packed with different concepts, and the main critique against "quick and dirty" solutions might've gotten lost in the mix. My bad for that. Specially, because it was the whole point for writing the article!

But the last tip, about shorter development cycles... is still possible even with complex software, but require advanced techniques. Some of them are found in the Bowling Game Kata of Robert C. Martin (look here for an updated version for JavaScript).

So, thanks for all, sorry for my poor writing, I'll try to be more clear in the future.

PS I've spent the last few months pushing people to not limit themselves to 'cosmetic' changes when resolving bugs, but to look for the root cause. I hope your comment will help to fix the underlying message.