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.
We've already had opensource projects threatened by the age-check legality nonsense (which cannot be enforced). If you regulate what features can/can't be in an OS you will end up negatively affecting opensource and/or hobbyists which will give the consumer less choice.
The only reason we have an actual alternative to Windows is because people create their own Linux distros and software around it.
I do agree that third party certification is one possible avenue.
Any sort of profession that warrants high quality service requires certifications (bar exam, USMLE, PE, etc)
Same goes for products too. It ’s not a reasonable solution for the consumers to perform an exhaustive research to get high quality guarantee.
I don’t find non official third party all that compelling. See Amazon marketplace as an example.
Similarly for eg a local carpenter. Or my tailor.
The bar exam merely tells you that someone is legally allowed to be a lawyer or some such. They don't tell you, if she's any good. I don't know what USMLE or PE are.
> Same goes for products too. It’s not a reasonable solution for the consumers to perform an exhaustive research to get high quality guarantee.
That's for the consumer to decide, isn't it? And consumer can use third party certification, if they want to, sure. (Or if they are required to do so by regulation.)
Software does not have regulation. In many areas of software we force shit quality on the users and just expect them to take it without complaint as a common practice. Then we as developers, like entitled children, completely rage the moment anyone casts light on this insanity.
Quality has more than one dimension. Food regulation is mostly concerned with "don't poison the customer". It doesn't otherwise care about things like taste or smell or texture.
Is eating spoiled food which gives you a disease better than not eating anything? No, it's worse, and therefore the minimum quality regulations make sense.
Is having low quality software better than not having any software? Yes, in almost all cases it is better. So a minimum quality regulation doesn't make sense.
When people put quality requirements too high on software, we get situations where for example public transport information and tickets aren't available digitally because the government is taking 15 or more years to make the "perfect" platform. The public is better served by a shitty solution the first years, an OK solution after that, and hopefully a good solution later on.
Delivering fast has a very important value when it comes to software, because you can replace it with improved versions at no physical cost. Delivering a vehicle which will kill you or food which will make you sick is very different. In those cases nothing is better than anything.
This is a common trope of the unregulated: We can’t raise quality because we can barely deliver as it is. The real message there is that the user should suffer so that you won’t.
I don't think anyone is required to insure a table or a wardrobe for decades, even in France?
The company might also go bankrupt with much of its profits having gone to owners and decision makers who are not bound to honor the warranty.
> The company might also go bankrupt with much of its profits having gone to owners and decision makers who are not bound to honor the warranty.
That's where reputation comes in.
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).
I can also remember when I worked at Travelocity a million years ago and they actively tried to fight this insanity with exhaustive A/B testing.
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.