Napkin Math Tool
taylor.town
taylor.town
As an example, "how long would it take for everyone in a large high school to microwave their meals if they all did it sequentially?".
People in a large high school is *4* (let's say about 3000 people).
Microwaving a meal is *2* (let's say 5 minutes).
So by Napkin Math we get 4+2=*6* which is a *large metropolitan area*.
Oops. I mean 11.6 days.
And with normal multiplication, 3000 * 5 = 10.4 days, so 11.6 days is a pretty good estimate.
So I think the answer is indeed "add the numbers together to multiply them", and be careful that you understand what units you're using.
> 6 11.6 days, two-week vacation, waiting for a passport, healing from minor surgery
It could be useful for Fermi estimation, where you generally only care about orders of magnitude.
Yet, without explicitly saying it's about (base-10) logarithms, it is preaching to the choir - either you already know that, or won't learn either.
Pet peeve - while most numbers make sense, this not, by a quite a large number:
> -10 practically impossible, every atom in your body quantum tunneling simultaneously one foot to the left
I don't want to do maths here, but for a single particle to happen that, it would be a totally different scale (I don't know, maybe closer to -10^10^10).
For -9 it lists 'shuffling a deck and getting cards in perfect sequential order', which is closer to -68. Also being dealt a royal straight flush is more like 10^-6 unless you get more than 5 cards.
Not that I don't understand why, low probabilities are very tricky to get a grip on. And 'winning the lottery' sounds a lot more likely to people than it should, while having the exact same birthday as someone at work is a lot more likely than you might think.
Any suggestions for stuff I can put in the probability rows?
That does tend to be the best way to think about those probabilities. For any probability you can make it happen If you try enough times or with enough people you can try to force it to happen. Below -6 is a pretty wide range of stuff you can just barely make happen if you have enough people, enough tries and enough time.
It's only once you get to the 'wouldn't happen to 10^10 people in a million years' that you get to the stuff that you can be fairly sure has never happened. Matt Parker has quite a good video on it [1]. He settles on 10^-19 as something that you can be fairly sure has never happened (deliberately).
As for other stuff in the probability rows, maybe include a couple of well known paradoxes like the birthday paradox. And be clear what you're saying, things like getting dealt a royal flush depends a lot on the type of poker game.
They are harder to intuitively guess maybe, but it's still trivial to verify. I don't understand why the article would have so many mistakes, unless either the author just chose whatever numbers felt right (but then why write them down as a reference?) or just used chatGPT.
-2 hours minimum wage day's work, small coffee shop daily revenue
-1 days entry-level weekly salary, independent contractor daily rate
0 weeks average monthly rent payment, typical car payment
Is the difference in order of magnitude between the first two just one (-2 to -1) or 2 (E-2 hours vs E-1 days)?And how is "0.1 days per $1000" an entry-level weekly salary? Now we have days and weeks in the same sentence.
Other people are asking about how to use this "tool", I think it's just a rough reference. I almost see it as a kind of art/poetry, the way it's presented.
<meta name="description" content="Logarithmic tables for estimations.">Oh, it was a large scam? Hundreds of people participated? Basically if an extended family reunion or apartment building full of people. Not as hard to imagine.
The hope would be to better calibrate our own magnitude of reactions against the numbers we see
You'd end up with this big graph of values, that in theory you could traverse as deep as you want by just using the right units and multiplying. "[1-person's joules burned per hour by standing] x [1-standium's worth of people] x [4-football game's length in hours]"
A day is about 10^5 seconds. 10^6 seconds is about a fortnight. A year is about 10^4 hours, or 310^7 seconds, so a billion seconds is about 30 years.
Typically the numbers you're multiplying are vague enough that these numbers are more than accurate enough - e.g. if you want to support 20MB/s for a year, back of the envelope says 600TB, exact says 630.72. You typically picked "20" out of thin air, and unless you have a very* specific use case (e.g. fixed-rate video streams) it's probably only accurate +/- 50% at best.
- What CPU makes a thousand cycles per second?
- How is fastest electronic switching slower than fastest computer operation?
- AFAIK, DDR5 access time is -8 or -7, not -6.
- Earth rotation frequency is -5, not -1.
- Infrared frequency is more like 14 or 13, not 12.
Engineering math works like this: if it's an order of magnitude bigger, round it to infinity. If it's an order of magnitude smaller, round it to zero.
Prior to teaching, he'd spent a career working on missile guidance systems.
Alternatively, chapter 8 of "Realm of Numbers" touches on logarithms, and "That's about the size of it" chapter from Assimov on Numbers" includes a log-scale table of animal weights (from blue whale at 8.08 to Rotifer at -8.22)
2.8 hr, watching a movie trilogy
Dune: Part Two