I think that team sizes also affects WET and DRY. WET might not be preferable for bigger teams because you need to acknowledge that you wrote or at least saw something similar before.
DRY on the other hand, is arguably currently dealt with using code analysis tools (and probably why 'knowledge' takes a back seat). So the use of code analysis tools here makes it easier to implement in bigger teams. You can argue that you can do the same in WET though.
What's your thoughts on this?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting article Conlin!
I think that team sizes also affects WET and DRY. WET might not be preferable for bigger teams because you need to acknowledge that you wrote or at least saw something similar before.
DRY on the other hand, is arguably currently dealt with using code analysis tools (and probably why 'knowledge' takes a back seat). So the use of code analysis tools here makes it easier to implement in bigger teams. You can argue that you can do the same in WET though.
What's your thoughts on this?