manhnt

> 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?

What's practical application of this?

Can someone explain the US laws of export control around cryptography in layman's term?

But how to know if a company is REALLY a midstage startup or not?