[d0m3]

The concept of overengineering is good on paper, but in practice it's being overused and not understood precisely.

I see devs freaking out when you use the word abstraction now...

Suggest extracting business logic from a React component and you don't know anymore if someone is gonna raise the "overengineering" flag.

If you start a new project, do you not use any library or framework at the beginning?

Obviously you take decisions according to how much the project/feature is expected to scale.

If your estimation was too low, you might cripple your development at some point, and need a rewrite or at least some significant refactoring.

If it was too high, I guess you overengineered.

What matters is asking yourself the question, and of course as engineers we like to challenge ourselves into building the best possible solution, but we equally need to consider how likely it is that such a solution is never needed.