Agreed! I'll usually go one step further for early projects and lean towards 3rd time copy, 4th time refactor.

Example: So much early code is boilerplate CRUD, that it's tempting to abstract it. 9 times out of 10, you'll create a quasi-ORM that starts inheriting business logic and quickly grows omni-functions.

Eventually you may actually need this layer, assuming you're system miraculously scales to needing multiple services, datastores, and regions.

However this doesn't just apply to the obvious, and you may find omni-logic that made a feature more simple once and is currently blocking N new features.

Code is cheap, especially today. Complexity necessarily constrains, for better or worse.