When you’re hunting for bugs with a nondeterministic test, how many times should you run the test? The program might be deterministic: the same input produces the same behavior. Presuming you’re confident this is the case, you could fuzz the input for a while, hoping to catch bugs. But if your program is nondeterministic, you must not only give it random inputs, you must re-test it on the same input many times, hoping to achieve high branch coverage and catch rare bugs. I was at the first...| A. Jesse Jiryu Davis
Should the temporal logic of actions also do performance modeling?| emptysqua.re
Spend less time worrying about bugs. Leave that to us. Our platform continuously searches your software for problems, enabling efficient debugging of the most complex issues.| antithesis.com
What is a deterministic hypervisor and why do we need one anyhow?| antithesis.com
When I was in college I took two intro economics courses: macroeconomics and microeconomics. Macro was full of theories like “low unemployment causes inflation” that never quite stood u…| Joel on Software
When we design programs, we usually look for two kinds of properties: that “bad things” never happen and that “good things” are guaranteed to happen. These are called safety and liveness properties, respectively. These are properties that we want to hold true for every possible program behavior. “We always complete every request” is a liveness property. If our system has it, every program trace will complete every request. If it doesn’t hold, I can give you a example behavior wh...| Hillel Wayne