4 ms·
This reminds me of how chess tactics feel so obvious when I’m on a tactics trainer, yet I can’t identify them in games where they actually happen. Or code that
by thekiptxt 4y ago
This reminds me of how chess tactics feel so obvious when I’m on a tactics trainer, yet I can’t identify them in games where they actually happen.
Or code that “obviously” has a bug only after it caused an issue in production.
Would be nice if someone warned me before I do a PR: “ok, fyi there is a subtle but devastating bug in the new_feature.cpp”
- maest 4y agoThis is a class of "hard to find, easy to verify" solutions.
- na85 4y agoWell if debugging is the process of removing bugs from code, then logically the act of writing the code must be called "bugging" and the probability of having a bug in any new piece of code asymptotically approaches 1 with increasing SLOC ;^)
- dbt00 4y agoEvery program has bugs, every program has inefficiencies. Therefore every program can be eventually reduced down to a single instruction, which will be incorrect.
- Archelaos 4y ago> Every program has bugs Where is the bug in this programm? END
- stephencanon 4y agoWhat’s the specification?
- the_sleaze9 4y agoIt was supposed to return a generated image of Reverend Thomas Bayes in the style of stained glass.
- deleted 4y ago[deleted]
- smitty1e 4y ago> Or code that “obviously” has a bug only after it caused an issue in production. Cognitively, the mind filters out quite a bit of information for performance reasons. Are we biased in favor of reasoning that "sounds plausible"? My "hot dice" say "yes".