4 ms·
As anything it is just a tool in our toolbelt and should be used carefully. If our system contains same user validation in 2 places, changing it in 1 place may
by skatanski 4y ago
As anything it is just a tool in our toolbelt and should be used carefully.
If our system contains same user validation in 2 places, changing it in 1 place may lead to issues, which are difficult to discover. However forcefully implementing DRY everywhere can lead to coupling and lack of separation between modules and influence deployments, and work of different teams. Its more difficult to build context of the implementation, if one needs to jump from file to file. There’s a balance to when to use it or not.
- deleted 4y ago[deleted]
- Bost 4y ago> same user validation in 2 places, changing it in 1 place may lead to issues, which are difficult to discover. Disagree. Quicker discovering issues difficult to discover is actually a good thing. > Its more difficult to build context of the implementation, if one needs to jump from file to file. Agree. In general, I personally look at DRY as "It takes time to implement and/or understand it, but when it's done then it works and it will last." "It takes time" is something your boss won't like, but that's (mostly) not an issue if working on open source SW. No boss -> no pressure -> higher quality.