[jobposter1234]

It's a different perspective that believes most (tech) businesses these days are not failing because of their codebase. It's the school of thought that believes the effort invested in exceeding the Pareto principle in writing code will only have a marginal effect on likelihood of success.

Cutting corners during development may build technical debt, but for the first N iterations, it also saves time. The argument goes that it's more important to get more versions in front of your customers than to build the perfect codebase off the bat.

Also, in any startup, you're going to need to significantly adjust the codebase as your business changes products (pivots). All the effort invested up front on a feature that isn't relevant is essentially wasted.

Speed of iteration is the primary objective (to people who think this way).