4 ms·

Where is the typo? And the usefulness of your comment?

• mellavora 4y ago
  the typo is "non-pessimized code", which should be "non-optimized code". I see humor in thinking if my code is pessimistic enough. Have I assumed that the edge cases will happen and worked around them? Do I expect (and handle) crashes, i/o failures, network timeouts, etc? "code pessimism" could be an interesting metric. The typo in the other post was "superb owl" which should have been "super bowl". Several people on that thread enjoyed the typo, including a comment from CostalCoder saying "Please, please do not correct that typo!" https://news.ycombinator.com/item?id=31999048 https://news.ycombinator.com/item?id=31999048
  • _gabe_ 4y ago
    I think they used that term on purpose. Non-pessimized in this case is the same as optimized, and I believe it's a reference to this video https://youtu.be/7YpFGkG-u1w https://youtu.be/7YpFGkG-u1w
  • euiq 4y ago
    It's a term of art used by Herb Sutter, among others: https://stackoverflow.com/q/15875252 https://stackoverflow.com/q/15875252
  • hsn915 4y ago
    That's not a typo. But it doesn't seems that you are engaing in a good faith discussion so I don't think further elaboration is worth anything.