Street-Fighting Mathematics
mitpress.mit.edu
mitpress.mit.edu
There is also a second book by the same author which is a bit harder and more comprehensive, and also open access:
https://mitpress.mit.edu/books/art-insight-science-and-engin...
[0] https://ocw.mit.edu/courses/mathematics/18-098-street-fighti...
That short course looks like its still available on edx - though it's archived - I seem to be able to access the material.
But even Keep the Aspidistra Flying was basically mutilated by circumstance [1] and it's still a great book. So, I'll take the insults towards mathematicians with humour and actually read some of it—I often switch between grumpy rigour to applicative speed. We all need to earn an income.
[1] https://en.wikipedia.org/wiki/Keep_the_Aspidistra_Flying#Lit...
Edit: Just to be clear, my comment on mathematicians is not on your quote, but this quote from OP's post:
> an antidote to mathematical rigor mortis
If it is the quote you added to the bottom of your comment, my question still stands. That isn't an insult to anyone (certainly not mathematicians) but rather a comment that many people freeze up when it comes to mathematics (at least that was my interpretation).
The word "antidote" is used in the book's summary, which is defined as (via Google) "a medicine taken or given to counteract a particular poison." One could take the "poison" to be mathematical rigor, or something similar.
Perhaps this does not change your opinion, but I do not think the original comment was completely off base.
Immanuel Kant wrote about it [1] and many engineers have a varying degree of animosity towards pure mathematics. So, in the book's description they say this:
This engaging book is an antidote to the rigor mortis brought on by too much mathematical rigor, teaching us how to guess answers without needing a proof or an exact calculation.
I don't like the advertising, or the description if you will, as it basically tries to discount rigour. One can simply say it's an addition to the usual rigour of mathematics for the sake of daily street fighting style problem solving. The way they state it, however, it sounds like they are saying that rigorous math is not necessary.
My reference to George Orwell is simply that when he wrote Keep the Aspidistra Flying his publishers made him write a lot of things he didn't want to write, and they even specified the amount of words the books needed to have (which is is somewhat understandable, but limiting still).
[1] https://en.wikipedia.org/wiki/Critique_of_Pure_Reason. However, note that this is about metaphysics and one can argue that pure mathematics is not what he was critisising and that his work doesn't directly try to disprove the use of axioms, without which mathematics cannot exist.
You think the British intelligentsia would react kindly to an honest portrayal of the class system?
And similarly to Orwell's book, it seems like Street Fighting Mathematics does actually have interesting content, despite whatever the reason may be that they need an "antidote" for general mathematics.
I think the author meant the same thing as Feynman when he described the "Greek" and "Babylonian" approaches to mathematics.
For all but a select few (pure mathematicians), the "Babylonian" approach is a lot more fun. Both approaches are clearly necessary and useful in different settings.
With the advent of systems like the Lean theorem prover, the two approaches may start to see a lot more overlap.
Here's my favorite trick: the radians of an angle in a unit circle is equal to the length of the arc of that unit circle.
My interpretation is that I think you guys are missing the fact that the intent of my original comment is in the context approximations, from which you can see the use of the 'trick' is correct.
To break it down a little further: the trick I am referring to is in practice it's often convenient to scale approximations so that you can use the unit circle for calculations, since you can use the radians as a measurement of arc length. If it's not a unit circle, the angle != arc length, so that convenience is lost.
is what I was responding to. My point is this -- there is no derivation happening there. If it was pedantic, obvious and simple to you as you claim, I wonder why you claimed that it was a derivation.
To you the distinction between a definition and a derivation might be a pedantic one, I have doubts on whether that is an universal or even an useful position to have.
I know that these lumped models are standard in heat transfer calcs, but the application to humans is always interesting. It reminds me a lot of thermal comfort models built to represent human comfort relative to environmental conditions. They all tend to use simplified heat balances to model the heat exchange (with net loss/gain resulting in feeling cold, hot respectively), and there's a couple (Pierce Two-Node Model) which uses two thermal lumps, one for the internal core, and the other for the skin.
Nonetheless the thinness of the book and the foreword about applications and real world math are very promising. Maybe I should try it out. Any thoughts from someone who has read it?
- How many gas stations are there in Paris?
- How much savings does the leading bank of the USA have?
- Estimate the population of Indonesia (to someone who is not that familiar with Asia).
It's probably a great deal more complicated than these type of questions. But if there is a course like this and a student still feels as overwhelmed by these type of questions, then I feel the title should be updated accordingly.
The reason I'm also mentioning this is because I'm curious if anyone did both and can attest to whether one does get better at estimation questions like the one I outlined. If so, I just might want to take this course, as I'd like a deeper exploration on the topic than just consultant interview estimation questions.
FWIW: it was worth quite a bit :)
It was discussed on HN some time ago.
You can get better at them over time.
Questions like these spawn a handful of new questions, and those questions might recurse into more questions.
You can find multiple paths forward given what kinds of information you can collect and what kinds of metrics can be used. You can estimate what the accuracy will be from each hypothetical path and you can estimate how much work it will be to collect such information.
It isn't always necessary to solve these kinds of questions this second. Sometimes an interviewer might want a really rough estimate solved then instead of being presented with different paths of research, but imho it's always best to talk about paths forward first, and it is best to hash out and clarify exactly what they want and mean. Only then once it is clear they do not want high accuracy and a simple estimate, then you can do just that.
In the real world you almost never want a low accuracy instant estimate, so I imagine you would look good by showing you can build a path to figuring it out at a higher degree of accuracy than just some basic estimate.
For example, I need to reprocess some documents and don't know how many will be affected. The scope of the change means that it can't affect more than a few hundred thousand, and I know I can easily reprocess a few million before it becomes an issue. I can leave the estimate there, even though it's "between one and 500k" because all I really need to answer is "is it under 3M?". Similarly there are cases the other way where I know quickly that the scale means certain approaches aren't possible despite not really knowing what the actual value is.
Learning how to identify what questions are important and easy to answer quickly has been something very useful.
Personally, another thing I find it useful for is for salary negotiations when you're talking face to face. Simply being able to guestimate a company's revenue, amount of clients, cost and their mindset gives you an idea if a low ball or high ball offer is due to mindset or due to finances.
I find in general that estimations of these types are amazingly good for when you really only have a few seconds, or to warrant further inspection. Like you said, if something is orders of magnitude away, then you already know the answer.
Taking a stab in the dark here but it might be because YC is mostly software engineers and these kinds of problems rarely fit into the domain. It's a useful skill set, absolutely, but isn't something taught in computer science.
On the data science side this has to be used all the time for most problems, but there are not many data scientists or other kinds of analysts on YC, so the kinds who use these tools are more than likely not going to be represented.
At the moment it's slightly more upvoted, I wish I could actually see all upvotes and downvotes as it'd tell me how controversial my comment is.
Personally I have seen many textbooks available in the US/Canada version and Indian Subcontinent version (generally the same text, often for sale at <25% the price). My guess is that it's common to see India in particular because there is a large market for English-language textbooks there.
huh?
[0] https://www.amazon.in/Abstract-Algebra-3ed-David-Dummit/dp/8...
Reasoning by analogy sounds dodgy to me.
I've always found that it's difficult to get a student to even venture a guess about the answer to a problem. If they do make a guess then they probably have a mental model about how the situation should work... and then teaching becomes easy: either their model is good or it needs tweaking.
You gotta have the confidence to be wrong.
But using an analogy to infer something that hasn't been observed? Unless the analogy is very close to the subject, it doesn't make much sense to me.
https://books.google.com/books?id=_zQsDwAAQBAJ&lpg=PT54&ots=...
That said, I agree with you. IMO, systems that can't be factored into quantifiable components can't be modeled accurately -- i.e. analogies.
Like the field of economics, where too often, analogies that are based qualitatively on only one or two factors are often proposed as sufficient to explain the behavior of diverse international economies, IMO analogies have proven to be insufficient bases for larger theories.
Same goes for philosophy and science. Analogistic thinking too often leads down garden paths. Too untestable.
I imagine if you wanted to study fighting in a mathematical way, you would want to study experts. MMA fighters, boxers, Muay Thai fighters all optimize their bodies and technique toward effective fighting. I bet there would be interesting science/math there, but I doubt street fighting would actually yield much insight.
http://chirontraining.blogspot.com/2013/03/cofv8-monkey-danc...
related discussion: https://news.ycombinator.com/item?id=23429390
(to reply directly: leverage is useful, mixed game strategies are useful, beyond that I can't think of other applicable theories. Miller points out that non-posturing violence is usually as unfair as possible, so maybe big-O notation?)