Programming vs. Mathematical Curiosity
demian.ferrei.ro
demian.ferrei.ro
I was thinking about generating a graph of connected nodes like the one you did. But TBH, i really like the ones on Wikipedia[1], and didn't really feel like making something of equal quality hehe.
[1]: https://en.wikipedia.org/wiki/Kaprekar%27s_routine#Kaprekar'...
Why the need for a competitive division of mathematics and programming?
What the op did was math, and I’m unsure why the need to think of it as something else?
> I suspect a more maths-oriented person would go through this very differently. Maybe they’d try to find an elegant analytical proof, without the aid of a dumb number-crunching machine brute-forcing its way through. Or they’d try to generalize the problem to different number of digits, or different number bases.
Why drag “brute forcing” like this? Why drag yourself like this
> I don’t really know.
Exactly, so why imagine a divisive assumption?
I meant the post to be more of a personal story. Of what i, personally, wanted to explore when learning about the Kaprekar constant, and of realizing that my interest is more on the "programming" side of things (programming languages, "readable" code, etc) than the more pure maths side.
But i can see how the tone could make it seem that was a competitive division of sorts, especially the title. I'll try to take it into account for (hopefully) future posts.
Well while I have you, the message I feel I failed to adhere to in my comment was my interest in letting you, or others who follow their passion in math and programming, know that what you are doing is in fact “real” math!
Keep it up!
Your post made me click through a bunch of links in it. Thank you, but give me back that hour! ;P
Better yet, I’ll trade you a different rabbit hole.
Based on your post I think you’d really enjoy this “strange determinant” series from Timothy Gowers: https://m.youtube.com/watch?v=byjhpzEoXFs
> It is, but it’s also a bit unsatisfactory, no? A lot of the time the particular statement is less important than the way it was obtained—why or how is something works seems much more relevant to me than the binary question of whether it is true. A novel result more often than not also uses novel proof techniques, which may then be adapted to other problems. One may learn a lot more from the proof than even from the applications of the result.
> (Perhaps the author does has a point about the different mindsets :))
And thanks for the video recommendation. Added to my watchlist :)
[1]: https://lobste.rs/s/vkqqvl/programming_vs_mathematical_curio...
[1]: https://jekyll.github.io/minima/ [2]: the sidenotes are stolen from Tufte CSS: https://edwardtufte.github.io/tufte-css/
I think that it depends a lot on background.
My suspicion is that it's not easy for a random, untrained person to think in either. I think that a lot of folks here are programmers, trained (intentionally or just by experience) to think in programming terms, and so find that easier. I'm a mathematician by training, and so find it easier to think in that way—for example, I still sometimes find it hard to force myself to think about the fact that it might matter which of two computationally equivalent formulations of a problem one uses, just because one takes orders of magnitude longer than the other to execute.
Leaning on the compiler and staring at a segfault would have been pretty discouraging before Java, for example. Folks who may have given up may have found Python learnable or more forgiving. Once past that initial hump, and writing loops, operations against a database, and we're off to the races.
But there's plenty to practice in math, with textbooks even. Maybe we needed to learn to compute, do enough exercises calculating--the same as printf() and console.log()--to get the bits before proofs, before the higher-order ideas, could stick.