Feynman vs. the Abacus (1985)
ee.ryerson.ca
ee.ryerson.ca
There are people lauding and panning Feynman in this thread, but this story illustrates a very important lesson that I've seen a lot of very smart people fail to learn.
Whenever you're doing a calculation, especially if you're using a computer or calculator, make an approximate estimate of what the result should be. Don't just assume that whatever method you use will produce a correct answer.
A man with an abacus (or computer) is probably going to be faster than someone like Feynman most of the time, but he's also going to make mistakes. Big ones. He might not make them frequently, but mistakes always happen sooner or later. The trick is to catch them when they do happen. That's hard to do if you have absolutely no sense of what the answer should be. If, however, you start from a rough estimate using anything your brain can come up with, as Feynman does in his anecdote, you're a lot less likely to produce a badly wrong answer without realizing it.
If this contest had gone on long enough, Feynman would have been beaten badly in several rounds if he messed up a calculation and had to start over. The thing is, Feynman would know when this happened because the outcome wouldn't agree with his initial estimate. The man with the abacus would, eventually, have produced answers off by several orders of magnitude without realizing.
Rough estimates are important.
At some point it stops being luck.
Which is another way of saying what you're saying, I think.
> I had a lot of fun trying to do arithmetic fast, by tricks, with Hans [Bethe] [...] He was nearly always able to get the answer to any problem within a percent. It was easy for him—every number was near something he knew.
I could definitely see him totally making this up by working in reverse (decide to teach a lesson about mechanical vs. fundamental understanding, start with a tough operation, pick a mentally tractable number like a bit over 1728, tack on the simpler arithmetic contests before it to contrast and build tension), so I'm not saying it's a good argument for it being real. Just that it's tough to say one way or another.
I can only take so much of his writing. On a psychological level, I have thought about it over the years, and come up empty. I probally don't know enough about the man.
What got me thinking about it was one of his stories about the kid who could tell you what's wrong with your radio with his hearing.
I understand needing to protect your ego later in life when you didn't get the respect you deserved. In the stories, the trait started very young.
And maybe I'm completely mistaken? It just might be his way writing that has me wondering?
> I don't know how to do this on a small scale in a practical way, but I do know that computing machines are very large; they fill rooms. Why can't we make them very small, make them of little wires, little elements – and by little, I mean little. For instance, the wires should be 10 or 100 atoms in diameter, and the circuits should be a few thousand angstroms across.
You don't study mathematics just to improve your mental arithmetic. If mental arithmetic were the point, you'd just practice mental arithmetic for your whole mathematical education, rather than progressing to more advanced topics.
Background on how students train to do this using the Soroban (the Japanese Abacus): [2]
Another demo: [3]
Two nine-year-old girls play shiritori[4] ("a Japanese word game in which the players are required to say a word which begins with the final kana of the previous word") while adding 30 three-digit numbers flashed in 20 seconds: [5]
[1] - https://www.youtube.com/watch?v=7ktpme4xcoQ
[2] - https://www.youtube.com/watch?v=Px_hvzYS3_Y
[3] - https://www.youtube.com/watch?v=JawF0cv50Lk
Feynman vs. The Abacus - https://news.ycombinator.com/item?id=5849665 - June 2013 (33 comments)
x = a0 10^1 + a1 10^0 + a2 10^-1 + ...
If you write down x * x * x, you get something like: x^3 = a0^3 10^3 + 3 a0^2 a1 10^2 + (3 a0 a1^2 + 3 a0^2 a2) 10^1 + ...
Now equate this term by term to your goal, which is: x^3 = 1 10^3 + 7 10^2 + 2 10^1 + ...
From the first term, you get: 1 = a0^3
So a0 = 1, giving us an answer of 10 so far. Plug that in to the second term and you get: 7 = 3 a1
which gives a1 = 2---you always round down. The answer is 12 so far. We have a carry of 1, which we need to add to the next one. That gives us: 12 = 3 * 1 * 2^2 + 3 * 1^2 * a2 = 12 + 3 a2
Which leaves a2 = 0. So the answer is 12.0 so far.As you go further, there are more and more terms hence the "scaling" phenomenon you see. Every time you are solving a polynomial equation in one variable, where the solution is an integer 0 through 9; my guess is that on an abacus you do binary search instead of root finding. On paper this sounds easy, but on the abacus it sounds impossible—each of those adds and multiplies is its own crazy sequence of steps.
1729 decimal is 1001 duodecimal, Every kid raised in a duodecimal system that had to learn how to convert into decimal in order to interact with us barbarians knows this fact.