Live data from Hacker News

A Mathematician’s Lament (2002) [pdf]

maa.org

51–60 of 120 posts

Re: A Mathematician’s Lament (2002) [pdf]

#51
post #37

Please read the article with a critical eye, some of it is complete non-sense, for example: CALCULUS: This course will explore the mathematics of motion, and the best ways to bury it under a mountain of unnecessary formalism. Despite being an introduction to both the differential and integral calculus, the simple and profound ideas of Newton and Leibniz will be discarded in favor of the more sophisticated function-ba…

This kind of approach simply doesn't make sense

It was poorly explained there, but essentially that style of reasoning does work: http://www.amazon.com/Primer-Infinitesimal-Analysis-John-Bel...

And I at least find that approach easier and more useful. (I learned it from the Feynman lectures on physics, where he didn't axiomatize it; the above link does.)

Re: A Mathematician’s Lament (2002) [pdf]

#52
I've read this article several times at this point (it does tend to pop up everywhere) and it resonates with me but I'm not sure what to do about it.

I really want to experience the kind of math the author writes about; can anyone recommend a place to start as someone who has only ever done "fake" high school math? I'm in college now and I'm halfway through a computer science degree; I've tried a few times to break into theoretical math classes but I've found the bar for entry pretty high (especially when I only have room for one or two courses), with most classes and even peers asking for years of experience and "mathematical maturity." Have any of you ever succeeded in learning some math outside formal curricula?

Re: A Mathematician’s Lament (2002) [pdf]

#53

I read this a couple weeks ago and decided to try and find a math book that incorporates some history in it. I found Journey through Genius: The Great Theorems of Mathematics with some great reviews. I am working on an iPad app that pairs up people to mentor each other through books like this. It has video chat and a shared whiteboard, so it is ideally suited for discussing math. If anyone is interested in reading th…

Yes, a million times! Journey through Genius is an excellent book (I, too, had this book for a History of Math class). It's really appropriate for people of all different levels of mathematical maturity. It's aimed to be read by a pretty much lay audience. But it covers some interesting t material that you're likely not to have seen in an undergraduate curriculum (Heron's formula, cubic/quartic equations, Euler's windmill proof).

Re: A Mathematician’s Lament (2002) [pdf]

#54
This is how I feel about doing most coding tutorials versus the MIT intro to CS through python, or project euler.

When coding is presented as: - here is a problem - how would you solve this problem? - here are some hints to get you started

it is incredibly fun for me. when it is presented as:

- follow along - look what you did!

it can be a bit dry.

Re: A Mathematician’s Lament (2002) [pdf]

#55

Earlier quoted context omitted.

> whereas understanding sums and compounding processes ARE [terribly necessary as a matter of life and death, or even to a certain degree, quality of life or death]. That's not actually true.

in an ideal world, I would agree with you. We do however live in the real world.

Please give one example applicable to a reasonable majority of human beings on the planet at this current time where "understanding sums and compounding processes" are a matter of life and death.

Re: A Mathematician’s Lament (2002) [pdf]

#56

As an erstwhile math major (I couldn't hack the honors basic algebra class - the difference between a euclidean domain and a principal ideal domain got too confusing; but I rocked proofs in analysis) I have to say that the author is confusing Mathematics (which is an art) and Arithmetic (which is a skill). Part of what make the opening farce absurd is that musical skills and painting are not terribly necessary as a m…

> The difference between a euclidean domain and a principal ideal domain

A Euclidean domain is an integral domain where the Euclidean algorithm works. For the Euclidean algorithm to work, you need to be able to divide two elements and produce a remainder that's smaller than the divisor.

So an ED requires a notion of "smallness" (the Euclidean norm) which interacts with division in a way that makes the Euclidean algorithm work (remainder is always smaller than divisor).

A principal ideal domain is an integral domain where every ideal is principal (can be generated by one element). It can be useful for you to know that certain situations cannot happen, e.g. in a PID you can say, "Let I be an ideal of D, then I = ..." and do something with the generating element g. It lets you pass from an ideal to a single generating element in a proof, which may be a useful capability. The PID concept is also part of a taxonomy, since Euclidean domains ⊆ principal ideal domains.

Re: A Mathematician’s Lament (2002) [pdf]

#57
I love this article, but: what can a practicing math teacher take away from it? How can you apply this stuff if you still have to teach a standard curriculum?

I'm really asking -- my friend is about to start as a high-school math teacher.

I guess the first recommendation would be: motivate every new technique by starting with one or more problems that the technique helps to solve. (Here "problems" is meant in the Lockhart sense -- real puzzles, not exercises.)

But how often are "techniques" actually taught in high school math, especially algebra and precalculus? A lot of high school math consists of digesting new definitions, or the generalization of old definitions. A fair amount of it consists of learning theorems that go unproven, or that are proven (by the teacher) too quickly for students to understand where they come from -- and in general it isn't satisfying to solve a puzzle with a theorem that one doesn't actually understand.

On top of that... students have to spend time with problems before they become genuinely interested in their solutions, so progress would be slower with this method. It's not clear that you could teach a whole year's curriculum in one year like this. (And if you fail to do that you'll eventually get fired.)

Any insight? I believe that it's possible to teach math, even standard high school curriculum, in such a way that students are at all times intrinsically interested in what's presented. But it would be awfully hard to do at scale, at the standard pace, as a high school teacher would have to. How might a teacher start in that direction?

Re: A Mathematician’s Lament (2002) [pdf]

#58
We really need to teach people _how_ to teach induction, which is only done right when you put quotes around your Boolean statements; the "implies" symbol gets jumbled up with everything else otherwise, and not using it at all is passing up on a great tool. One can do simple proofs-by-induction without a single English word, completely symbolically, and have it be understood easily, if one uses quotes and correct LaTeX formatting (or good handwriting)

Induction doesn't just involve numbers and equality signs, it involves _statements_ with variables inside of them, and non-programmers need to be made well-aware of this (and taught Boolean logic early, PLEASE)

Re: A Mathematician’s Lament (2002) [pdf]

#59
Love this essay. I read it years ago when my brother was working with Paul Lockhart, who deeply influenced him as a math teacher.

My brother and his wife have since started an organization called Math For Love (http://www.mathforlove.com) focused on changing the way math is taught. They run workshops for teachers and provide great material for students.

If you're in Seattle and interesting in pedagogy and math, you should check them out.

Re: A Mathematician’s Lament (2002) [pdf]

#60
post #22

Earlier quoted context omitted.

Interestingly, the converse is also true. I was always into computers and tech but never really programming. I was a math major in college, however, and after graduating I started programming. The transition was almost seamless, I picked up programming really quickly, it was surprising to me how much the "ways of thinking" are alike.

Can't vouch for this book, but coincidentally just read about it today-- "The Essential Knuth" by Knuth, Daylight, and DeGrave. Donald E. Knuth lived two separate lives in the late 1950s. During daylight he ran down the visible and respectable lane of mathematics. During nighttime, he trod the unpaved road of computer programming and compiler writing. Both roads intersected! -- as Knuth discovered while reading Noam…

> (...) while reading Noam Chomsky's book Syntactic Structures on his honeymoon in 1961

Which makes you wonder, what kind of person reads this stuff on the honeymoon.

Post reply on HN