MVP is tool like any other. It might be used well (to validate an idea) or may be used poorly (to implement semi-functional piece of software, which is strictly

MVP is tool like any other. It might be used well (to validate an idea) or may be used poorly (to implement semi-functional piece of software, which is strictly worse than the peers). There's also nothing wrong with pivoting, because while you may implement working businesses case, along the way you may discover one, that's better for you and your customers. Of course it can be used in pathological manner as any tool again. I think, that what should be definitely busted in IT(or maybe in general?) is easily talking in absolutes (OOP best/bad, functional programming best/bad, k8s best/bad). Everything depends on the context. Especially would be great to see that altitude from members of academia, because they influence a lot of young engineers.