> Make it fail: Do it again, start at the beginning, stimulate the failure, don't simulate the failure, find the uncontrolled condition that makes it intermittent, record everything and find the signature of intermittent bugs
Unfortunately, I found many times this is actually the most difficult step. I've lost count of how many times our QA reported an intermittent bug in their env, only to never be able to reproduce it again in the lab. Until it hits 1 or 2 customer in the field, but then when we try to take a look at customer's env, it's gone and we don't know when it could come back again.
Is an "average modern high-end car" just a bunch of computers connected together? Each of them is running its own software. Then is the total number LOC in a car actually the total number LOC in each of these computer added up?
Except there may not be any Lines Of Code in any of those computers. The code is the blueprint to make the machine not the machine itself. The program, or binary as some like to call it, does not really come in lines.
We put the end visualisation on our team shirts. Unfortunately due to printing limitations it didn't end up looking that good, but it's still a neat idea.
Best i recall, from back when the PGP thing was going down, was that anything above 90-bit keys (or some such) was basically considered the equivalent of a military weapon.
So if you wanted to offer it to anyone outside of USA, you were treated as if you were trying to deal in tanks or fighter jets.
Unfortunately, I found many times this is actually the most difficult step. I've lost count of how many times our QA reported an intermittent bug in their env, only to never be able to reproduce it again in the lab. Until it hits 1 or 2 customer in the field, but then when we try to take a look at customer's env, it's gone and we don't know when it could come back again.