"Premature optimization is the root of all evil" More and more, I'm realizing this applies more broadly than just for code. Abstraction is a form of optimization and shouldn't be done before the space has been properly explored to know what abstractions should be built. Standardization is a form of optimization and shouldn't be proposed until there's a body of evidence to support what's being standardized. Failure to…
> Failure to validate a product before building it? Premature optimization. I largely agree with your comment, minus this. Unless everything after the initial idea for a product is an "optimisation" - which is quite a claim - building something shouldn't be lumped together with optimising it. My point is that it seems like you're attributing more to this idea than is fair.
Building a product before a good indication it is the right thing to build is prematurely optimizing a business.
At any level of a project, it is important to do things in the right order, to avoid wasting unrecoverable time and effort on work that never needed to be done.