I think you generally shouldn't create an abstraction until you have at least three uses for it. That's very generally. You might want to create abstractions b

I think you generally shouldn't create an abstraction until you have at least three uses for it. That's very generally. You might want to create abstractions before then, but be prepared that they will be wrong, and don't invest in e.g. lots of unit tests, because when you break the abstraction you'll throw away that work. Some unit tests yes, but more in semi-integration tests that verify the stack sandwiching the under-proven abstraction.