Do you think it should be acceptable to break the DRY Pattern in some cases? For example repeating db paths in events and subs is more readable but referencing a path variable located elsewhere is more DRY. Also some view code is easier to understand if it's just repeated but then it wouldn't follow dry. Another example is some forms. A login, signup, password-change-request and password-change page duplicate a lot of similar fields such as email & password. Its more readable to to just duplicate the events and subs and when you need to make small differences its easy to do. For example the password field in login may have different validation to signup. Keeping this DRY complicates the code but it's DRY. afaik the DRY pattern exists to prevent making changes in many places but it's a trade off with complexity. What are some peoples thoughts?