3 ms·
Agreed. Also one can get over-eager with abstractions over things that are not real duplicates. They just happen to look similar at this moment in time. In th
by smoe 7y ago
Agreed.
Also one can get over-eager with abstractions over things that are not real duplicates. They just happen to look similar at this moment in time.
In this category, I would also put premature automation before learning what it actually is you are automating among other things.
Or more generally: Don't try to be clever about something you don't (yet) understand.
- chubs 7y agoI once read a guideline (by DHH I think?) "One, Two, Refactor" as in write it once, then duplicate it, and the third time think about refactoring it to be DRY. But yes it's all about discerning what's reasonable given the circumstances, and not being dogmatic.