My dad (an engineer not a mathematician) would use Newton-Raphson[1] to solve basically any problem that wasn’t very obviously linear. When I was a kid, some of my first programming memories were my dad getting me and my brother to implement Newton-Raphson in basic on an HP85a, getting me to implement Newton-Raphson in rpn on an HP calculator, debugging my dad’s (genuinely revolting) basic program[2] which wouldn’t r…
My dad was also an Engineer. He was also a Fortran fan. Once he asked me to explain OOP. After I explained the basics he said it was useless and never looked back.
Every mathematician has only a few tricks (2020)
61–70 of 87 posts
Re: Every mathematician has only a few tricks (2020)
#62My dad (an engineer not a mathematician) would use Newton-Raphson[1] to solve basically any problem that wasn’t very obviously linear. When I was a kid, some of my first programming memories were my dad getting me and my brother to implement Newton-Raphson in basic on an HP85a, getting me to implement Newton-Raphson in rpn on an HP calculator, debugging my dad’s (genuinely revolting) basic program[2] which wouldn’t r…
Re: Every mathematician has only a few tricks (2020)
#63Earlier quoted context omitted.
For me, it's tracing code/pipelines to figure out how a result was produced, typically in the context of that result being wrong somehow. Go To Definition is the most useful function in any editor. I'm always surprised by how frequently colleagues don't think to do this and are left helpless.
This reminds me of my further theory that everyone needs one 'heavy' and one 'light' technique. The 'light' technique is something that often works well as a heuristic and can be an effective unit of iteration. The 'heavy' technique is something that you can fall back on in difficult cases, something that can reliably solve hard problems, even if it's slow. Sometimes the heavy technique is: just ask someone else. ;)
Re: Every mathematician has only a few tricks (2020)
#64Earlier quoted context omitted.
This reminds me of my further theory that everyone needs one 'heavy' and one 'light' technique. The 'light' technique is something that often works well as a heuristic and can be an effective unit of iteration. The 'heavy' technique is something that you can fall back on in difficult cases, something that can reliably solve hard problems, even if it's slow. Sometimes the heavy technique is: just ask someone else. ;)
I have both felt and seen this at work and I would add to this the meta-technique of binary search. Once it is added to your light and heavy technique you can solve what seems intractable at first glance faster than many people can even orient to the problem.
Re: Every mathematician has only a few tricks (2020)
#65My dad (an engineer not a mathematician) would use Newton-Raphson[1] to solve basically any problem that wasn’t very obviously linear. When I was a kid, some of my first programming memories were my dad getting me and my brother to implement Newton-Raphson in basic on an HP85a, getting me to implement Newton-Raphson in rpn on an HP calculator, debugging my dad’s (genuinely revolting) basic program[2] which wouldn’t r…
I fear not the man who practiced 1000 kicks but I fear the man who practiced one kick 1000 times
Re: Every mathematician has only a few tricks (2020)
#66My dad (an engineer not a mathematician) would use Newton-Raphson[1] to solve basically any problem that wasn’t very obviously linear. When I was a kid, some of my first programming memories were my dad getting me and my brother to implement Newton-Raphson in basic on an HP85a, getting me to implement Newton-Raphson in rpn on an HP calculator, debugging my dad’s (genuinely revolting) basic program[2] which wouldn’t r…
Re: Every mathematician has only a few tricks (2020)
#67Re: Every mathematician has only a few tricks (2020)
#68My dad (an engineer not a mathematician) would use Newton-Raphson[1] to solve basically any problem that wasn’t very obviously linear. When I was a kid, some of my first programming memories were my dad getting me and my brother to implement Newton-Raphson in basic on an HP85a, getting me to implement Newton-Raphson in rpn on an HP calculator, debugging my dad’s (genuinely revolting) basic program[2] which wouldn’t r…
My dad was also an Engineer. He was also a Fortran fan. Once he asked me to explain OOP. After I explained the basics he said it was useless and never looked back.
Very rarely, however, do you see a brilliant mind like Richard Feynman, a man who was so open to new ideas and out of the box thinking. Even in old age. Seeing someone, in good faith, question what they believe in light of new knowledge is very rare. Now that is a special thing.
Re: Every mathematician has only a few tricks (2020)
#69Earlier quoted context omitted.
“The most successful people have failed more times than you have tried”
Success is relative. If the goal is to never fail, never try is the best strategy. Also the most sure path to finish in the 1% wealthiest is to start in its network. When the game is set to make 99% of players considered as losers in its own terms, the best strategy to have fun at scale is to not care about the highlighted goal. Keep awareness of how rules actually apply, take shortcuts if it feels safe and preferabl…
This is dangerously not true, if you never try, then you are guaranteed to fail to live up to your potential, which is one of the greatest failures of all.
Re: Every mathematician has only a few tricks (2020)
#70Earlier quoted context omitted.
“The most successful people have failed more times than you have tried”
Success is relative. If the goal is to never fail, never try is the best strategy. Also the most sure path to finish in the 1% wealthiest is to start in its network. When the game is set to make 99% of players considered as losers in its own terms, the best strategy to have fun at scale is to not care about the highlighted goal. Keep awareness of how rules actually apply, take shortcuts if it feels safe and preferabl…
With that said, I think you make some good points about the perspective people should have about competitive goals. Most contests are not strict meritocracies, and you are in for a lot of frustration if you assume that only effort matters when other slide by on their structural advantages. I would prefer to reframe the goal as 'work hard on what you have control over, as long as it provides some amount of benefit, and as long as you still care about the outcome.'