
Originally Posted by
Rodolfo Paiz
I fully agree that some parts of the software are safety-critical and those deserve much, much, MUCH tighter scrutiny and controls than other parts of the codebase. I also agree with you that, because we're all human, someday a problem will almost surely happen, and we can but pray that it doesn't kill anyone.
That being said, I disagree with your proposed solution. The FDA is fundamentally broken, with science being all the way at the back of the bus and lobbying/corruption driving. The air-traffic-control software is, if at all possible, even worse. The FAA is billions over budget and years behind schedule on just doing the basics right... the system is safe because pilots and controllers keep it so, but no (or not much) thanks to the guvmint.
Government oversight is great for some things, and absolutely necessary for others: but in this case, I think you're giving it WAY too much credit. I have no faith that a government programmer is highly likely to spot a code problem in Tesla code and/or that the potential safety benefit of that attempt is worth the huge cost (in time, money, resources, delays to customers, and just reduction of the overall value of the product) this would entail. Government oversight of firmware revisions is not, IMHO, the answer here.