Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login
user: Leo_Germond (* users last updated on 10/04/2024)
submissions comments favorites similar users
created: 2021-06-24 08:16:04
karma: 162
count: 63
Avg. karma: 2.57
Comment count: 61
Submission count: 2
Submission Points: 4
about:


user: docandrew (* users last updated on 10/04/2024)
submissions comments favorites similar users
created: 2017-10-23 21:40:20
karma: 1364
count: 335
Avg. karma: 4.07
Comment count: 335
Submission count: 0
Submission Points: 0
about:



None

As powerful as fuzzing is, this is a good reminder why it’s not a substitute for formal verification in high-integrity or critical systems.

The advice about if up is not bikeshedding though, it is the exact kind of architectural choice you're saying one should decide on. Don't believe me ? Well imagine you have inputs, where should you validate them ? According to this rule of thumb it's at the topmost level, when they are received. Well that seems super sensible, and it's typically something that helps with understanding the code (rather than checking them at thw very last moment). Also for proofs that's technically necessary to allow the preconditions to "percolate up", which has the same effect of moving the if up.

So the first advice is definitely not bike shedding, the second one I'm not so clear though ;)


Exactly, there’s a fine line between prioritization and bikeshedding.

Legal | privacy