My rule for major new abstract components is: “if you’re going to do that, you have to get it right”. It’s fine to have a major abstraction, but it needs to ac

My rule for major new abstract components is: “if you’re going to do that, you have to get it right”. It’s fine to have a major abstraction, but it needs to actually make a problem space disappear, for some definition of “entirely”. That means: - great code - great documentation - tested - engineering resources assigned to maintain it full time ... for as long as it takes. Until you reach that level of “makes the problem space disappear entirely”. So when someone suggests a new abstraction, I just ask if we’re going to invest all of that. And if not I suggest we stick to just using the tools we already have.