I noticed a great overlap in learning math and programming.
Programming was easier for me to learn and now helps me to understand math a bit better.
Coding a real project is the equivalent to math's proofs, I think.
The book "Badass - Making Users Awesome" says, learning something just requires two steps. Perceptual exposure (of hundreds of correct examples) and deliberate practice.
I think, math falls short in the first step, and I don't know why, but somehow mathematicians often see much part of syntax/grammar as a given, and use different ways to describe the same thing (sqrt and power of 1/2, for example).
But, then does programming. In C, there's at least three (arguably more) ways of doing a loop.
You can use for (...) { ... }, you can use while (...) { ... }, and you can use do { .... } while ( ... ).
Of course, which one you pick depends on context. But, then, which one of sqrt or "raised to 1/2" you choose also depends on what's more convenient at the time.
Programming was easier for me to learn and now helps me to understand math a bit better.
Coding a real project is the equivalent to math's proofs, I think.
The book "Badass - Making Users Awesome" says, learning something just requires two steps. Perceptual exposure (of hundreds of correct examples) and deliberate practice.
I think, math falls short in the first step, and I don't know why, but somehow mathematicians often see much part of syntax/grammar as a given, and use different ways to describe the same thing (sqrt and power of 1/2, for example).