I don't know how this article made the subject of the weekly newsletter: "DRY is out, WET is in". This is really not a good practice to follow. I think we should simply understand the basic term of DRY and that's it. When you say duplication is not a problem, things might get out of hand. I agree with some of your discussions, but I still feel that the DRY term has its own importance in both the programming and development world. If you code something twice, it also means you have to maintain and update something twice. This argument can be indefinite.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.