I reckon that all things equal, bad code quality in itself does not increase the chances of success. Bad code quality may be a symptom of rapid iterations and

I reckon that all things equal, bad code quality in itself does not increase the chances of success. Bad code quality may be a symptom of rapid iterations and not burning too much cash on development prior to achieving product-market fit. Ability to rapidly iterate and having enough cash to continue operating would both increase chance of success. On another hand, it could be possible to have glacially slow iterations while burning truckloads of cash and still have low quality code. E.g. hiring an unnecessarily large team of high-priced developers who are not competent, or trying to operate in the context of some existing complex legacy environment that impedes rapid iterations and delays feedback signals.