Urgent.News

What's breaking now, across thousands of outlets.

Tech

Knuth reward check

Twenty years ago, I received one of the most remarkable letters ever. Computer science legend Donald Knuth discovered an error I had found in one of his books and sent me the highly sought-after check. This practice of rewarding error finders is well-known in the computer science community as Knuth's "reward for any error" policy. It's an extraordinary event, considering the countless individuals who have scrutinized his works, including those who are far more knowledgeable and diligent than myself.

Upon receiving the letter, I had initially thought I had uncovered an error, but upon further examination, months later, I had to admit my mistake. This was due to the positional nature of the error: it was in the very first word on the first page of the book "Computer Modern Typefaces." This particular book is less popular than others like the TeXbook or The Art of Computer Programming, and it's placed in Volume E of the Computers & Typesetting series, making it a somewhat obscure reference. The Memo field for this error is noted as "E1".

Due to Knuth's concern about potential misuse of the check's numbers, I received a fantasy certificate and an amount of $2.88 from the Bank of San Serriffe. This amount is represented as 0x$1.20 in my records, which equates to $2.88 in decimal. A few years later, I submitted another proposed error, but unfortunately, my submission was incorrect. Knuth not only provided a detailed explanation of why I was wrong but also rewarded my persistence with another check for $0.32.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at thomas-huehn.com →

More in Tech

How Do We Extract the “Why” from a PR into a CHANGELOG with Jev? 🤔

Hoi hoi! 👋 I'm @nyaomaru , a frontend engineer currently building an AI-assisted CHANGELOG generator and experimenting with Jev. 😸 Recently, I have been thinking about one problem. How can we extract this ## Why The previous implementation could leave stale release data after an update. from a pull request and put it into a CHANGELOG?

More from Saturday 10 October →