Hacker News Reader

Comment by thekiptxt | Hacker News Reader

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”

View on HN

Well 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 ;^)

Every program has bugs, every program has inefficiencies. Therefore every program can be eventually reduced down to a single instruction, which will be incorrect.

> Every program has bugs

Where is the bug in this programm?

END

What’s the specification?

It was supposed to return a generated image of Reverend Thomas Bayes in the style of stained glass.

This is a class of "hard to find, easy to verify" solutions.

> 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".

Reply on news.ycombinator.com