3 ms·

Generally, it is considered preferable to find problems as early as possible. If a program fails to compile or quickly crashes (because of a failed assertion),

by okl 6y ago

Generally, it is considered preferable to find problems as early as possible. If a program fails to compile or quickly crashes (because of a failed assertion), then I consider that better than having to unit test and fuzz test your code to find that particular problem. As an added benefit the code also becomes more robust in the production environment, if there are use cases you failed to consider -- 100% branch coverage does not guarantee that there are none!

dllthomas 6y ago
> Generally, it is considered preferable to find problems as early as possible. Whole heartedly agree. > If a program fails to compile or quickly crashes (because of a failed assertion), then I consider that better than having to unit test and fuzz test your code to find that particular problem. This confuses me. My typical order would be: fails to compile > unit test > quick crash at runtime > slow crash at runtime (fuzzing) I am curious to understand why we differ there.