Ultimately it’s a way of saying “I have no vision so I just want to quickly throw a bunch of shit on the wall and see what sticks”.
You start off with a hypothesis (X will solve Y's problem by doing ...), you build a prototype, and then you start testing with multiple Ys. Based on that feedback, you then tweak your initial hypothesis or you scrap it and pivot.
The whole point of engineering is to build tools that solve a specific class of problems for the buyer.
A famous person once said the customer doesn’t know what they want until it’s shown to them. And it’s true.
If you wanna go ahead and pretend you’re superior to Steve Jobs, go ahead fella.
Thus, for most folks releasing a product and getting to market/revenue is more important than anything else. Then iterate from there.
YMMV of course. But the older I get, the more I realize "just get it done" is far more important than almost any other metric there is. There is a ton of navel gazing in tech that provides negative value. If I had released some of the things I worked on in the past vs. carefully designing and polishing them, I might still be working on them today. Competing products have maybe 50% of the "quality" of even my prototypes of 10 years ago - but they exist in the market and are used every day by customers to generate income.
That's the test part, is it not?
Yes it led to some degree of tech debt, but it also made it easier to experiment, validate, and identify good and bad workflows.
At least in my network, we don't think AI will replace all workers and we strongly believe AI will lead to a significant amount of tech debt, but we do also recognize a lot of work in tech today is busywork and will be automated away in the hands of actual engineers with domain expertise.