DRY is priceless, and if your argument is to avoid DRY in very specific cases, state that specifically. DRY, when used with functional, well named code is the

DRY is priceless, and if your argument is to avoid DRY in very specific cases, state that specifically. DRY, when used with functional, well named code is the number one thing keeping a codebase easy to read. There should be one way to achieve something well-defined like save/edit/delete an entity, check a file type, url encode a string, etc. This ALWAYS leads to much easier code fixes AND much easier refactoring.