There are economic impacts to raising quality:

1. Higher quality requires better trained technicians. That means fewer people will be able to participate due to any of missing experience, costs of training/education, and opportunity costs.

2. Higher quality generally requires third party certification, such as the CE or FCC identifiers on electronic equipment. Certification costs time and money resulting in a form exclusivity.

3. Higher quality means goods/services with increased durability, which requires fewer updates or repurchases. That is great, for the producer, if everything comes with a warranty but is bad if patching is an extra expense.

Now consider what that means for software, a fully unregulated industry. It means some form of credentials for developers instead of frameworks or tech stacks. It means paying money to third parties to validate every patch release. It also means applying a warranty to all commercially licensed software. These things would raise the price of software and eliminate most people currently employed.

"Now consider what that means for software, a fully unregulated industry. It means some form of credentials…"

So what! Until the 20th Century pharmaceuticals/medicines were unregulated (eg: buy laudanum (opium) anywhere without regs and instructions said it was fine to give it to kids). After deaths, disasters and addiction regulations tightened—especially so after birth defects and thalidomide. Now the industry is tightly regulated.

Right, it took over one hundred years for pharma to be regulated. So be it for software. It's time the Wild West came to an end.

There'll always be whingers along the way, especially if they stand to lose profits. The "Good Times" for the software industry ought to be over because consumers are no longer benefiting in the way they should. Want a quintessential example of 'junk' software: Windows 11.

I don't buy your list. For example, higher quality doesn't require third part certification. Reputation (and warranties) can work without third parties.

I do agree that third party certification is one possible avenue.

I don't think the idea of circular economy, where goods are produced with high manufacturing quality standards, applies to software. In the sense that producing high quality physical goods may not be beneficial for the producer. But producing high quality software is rarely not beneficial for the developer, specially in the long term.

Maybe idea could be maybe applied to the offering of long-term technical support and backwards-compatibility (in terms of durability of the software) and open source (in terms of reusability of the software).

Not to mention, it would raise the cost of Software as a Service businesses as the cost of building and maintaining software goes up, as well as the technical expertise to maintain those systems. That would have a flow-on effect of reduced market as low-medium income folks are effectively priced out of the market, no long paying for "cloud services, and so on... It would be a disaster.

As far as I can see the linked report does not mention software at all. It is all about physical products.

I think all three of these points, but especially the first two are rather speculative; I don't personally believe they hold, though I can't be sure.

Most quality defects I see are ultimately down to culture, not training and certainly not certification. Getting to excellent quality simply does not require great training nor rigorous certification, and I'm not even sure it really benefits from either all that much. But what it does require is a culture of chasing down all the avoidable risks, to fix not just the immediate bug, but also the process that allowed it to come to be, to pre-emptively look for whole classes of bugs or misfeatures seriously, and to always look deeper than for underlying causes or interactions (i.e. take the 5-why's game seriously).

It's perhaps almost a trope by this point, but it's still a great reminder and example - sqlite. About a month ago Richard Hipp, one of the primary authors, gave a great presentation "Reliability Lessons From SQLite" (https://youtu.be/V_qzqY1bb7I) - and notably, I'm not seeing even _echos_ of training and certification in their clearly world-class process. I don't think you can even seriously claim it's all that expensive, if you consider how tiny that team is, and yet how much they've achieved.

If larger organizations fail to achieve high quality - well, _why?_ It's not due to lack of training, certifications or smart people. Perhaps its intrinsic about larger for-profit corporations, but I suspect we could do better with better incentives, and a more serious attitude about dealing with mis-aligned incentives throughout our culture. Is it really a flaw for a corporation to prioritize short term cost reduction even over long term self-harm if that's what they're judged by? Is it a flaw for a profit seeking corporation to largely ignore costs their low quality imposes on others? Is it a flaw for a for-profit organization to take huge risks when the upside is unbounded but the downside is mere bankruptcy without any further liability?

I don't know how to solve these problems, and don't want to claim it's even remotely reasonable to throw out the capitalist baby with the corporate bathwater, but surely we can do better than the status quo even without a revolution. Misaligned incentives and tragedies of the commons aren't new issues, nor ones without potential mitigations. We're just choosing to ignore those inefficiencies, and have for decades. And at this point, even small changes in incentives might have truly wrenching consequences; the ingrained and by now deeply embedded carelessness in our huge software and other engineering stack is corroded at every level.

TLDR: I don't have the answer, but I'm pretty positive it's not an issue of cost, training or certification.