[RowanH]

So semi related, been in software for 20 years and contemplated getting a Motec w e-throttle for my (road legal) race car "no f-king way" is my thought process, I've got a race engine management system but no way I'm having anything other than a cable between me and the throttle body. I love software, I love engineering, I love what an e-throttle can do for traction control. But there will always be bugs with software ...I'd trust a road car with massive engineering teams, I struggle with the thought of a smaller team and how it could possibly go wrong. I personally get where he's coming from ... I can't imagine single engineers being able to test and have foresight on the umpteen permutations of "what-if"

[kodfodrasz]

I have worked in automotive and the testing of a software release took about 1 month for a ~150 member team. Yes, documentation because legal requirements was as much as 10% of the human labor, but the tests ran for a month in simulated environment.

This was not a particularly large software, about .5MLOC total with 3rd party RTOS as well (not in our test scope).

The tests did find unexpected bugs, as the dynamic behaviour of the system was much harder to reason about than about the single components, and sometimes pretty weird system effect kicked in.

I'd also not trust this to small teams, this is simply way more complicated than one presumes prior to experiencing it personally.

[dotancohen]

> I can't imagine single engineers being able to test and have foresight on the umpteen permutations of "what-if"

Maybe the answer to this is to have the software unit tests open source as well, and document the hardware integration tests (including spectacular failures) on Youtube.