WET
As opposed to DRY, WET is Write Everything Twice.
Generally it's a good advice which may be be paraphrased also as:
- don't abstract too early
- don't generalize too early
Having 2 (or better 3) copies gives you a good understanding which part is common and which is specific for each copy.
Meta
Created: 2021-10-02
References:
- https://overreacted.io/the-wet-codebase/ - a talk by Dan Abramov (I hadn't watch it yet)
- Split, but sometimes merge - a common action for DRYing code is extracting common part (split). But sometimes another action preferable: merge some parts, functions into one