I can and have explained beautiful proofs without the need for mechanical proficiency to ten year olds and mathphobes alike. Here are a few examples:
[1]: http://jeremykun.com/2011/06/26/teaching-mathematics-graph-t... [2]: http://j2kun.svbtle.com/things-mathematicians-know-proofs-ar... [3]: http://j2kun.svbtle.com/things-mathematicians-know-more-than... [4]: http://jeremykun.com/2011/06/26/tiling-a-chessboard/
The world is full of these cool problems and proofs. I could literally teach an entire course and do nothing but puzzles involving chessboards. That many teachers ignore these great topics is a problem, but it's certainly for a good reason (the myriad of other problems with high school education).
There is this awful commercial in the states for an online tutoring project where the student asks "how do I find the area if a triangle?" The response is "well, Cindy, the formula for the area of a triangle is 1/2 b*h, so you take half the base and multiply by the height and that's how you find the area of a triangle."
Non of that is false, but all the poor girl in the commercial learned was yet another reasonless recipe.
Recipe's are a very helpful fallback where you might be struggling with understanding the origins of material in a rigorous manner. You can inspect a triangle all you like, but at the end of the day it's much easier to simply remember the formula.
This, I am finding, is the only way I'm managing to actually understand complex analysis - take the formulas for the results, and remember how to apply them. It's revealing to me that what looks complex gets very simple in that manner (and also that I still get tripped up by elements of basic integration).
If I couldn't do this, then I'd be lost - and in a test simplification remembering how to work through the definition isn't possible (and isn't required thank god) because that's a path which leads to me spending 6 hours figuring out and trying to picture something in a way which makes sense.
Well yeah, it would be really inefficient to derive the formula and then plug numbers into it, but you don't have to do that, you can just teach people to complete the square instead. It's pretty much as fast as using the formula (since it's the same operations), but it builds on your existing equation manipulation skills and so you understand every single step. And if you ever need to actually know the equation for whatever reason, you can derive it easily.
I'd rather spend our children's time letting them know that these formulas exist, making sure they can perform them as needed, and then have them move onto something new. No need to drill / memorize trivial (as opposed to fundamental and foundation) stuff that is 2 seconds a way with google.
The worst kind of math education was that endless dribble associated with memorizing useless patterns that could easily be looked up in a book. At one point I had (painfully, oh my god, so painfully) memorized about 20 different patterns so I could chunk up integrals into products of u(x)v(x)only to spit them back on exam day, and never again look back on any kind of calculus. That was not a pleasant day week in high school. Would have been much better spent learning Geometry, Prob/Stats, Discrete Math, Linear Algebra, or any other host of mathematically oriented topics.
Personally, it think the time for manipulation of symbols has passed. Math should be only about concepts and hardware or software should do he manipulation. But then you run into systemic issues like "how do I test all students". The factory-styled learning environment needs to die.
It seems to me that training to derive a lot of stuff would enable them to solve more kinds of problems, would it not?
Could someone have told us that in high school?
Anything of degree 5 or higher is not guaranteed to have solutions solved by radicals (that is, a solution that can be expressed as some rational number to some exponent). For example, x^5 - x + 1 = 0 cannot factored into linear and quadratic polynomials in this way.* The proof for the insolvability is actually quite elegant.
Even so, factoring a polynomial from degree 3 or 4 into quadratics or linear terms is hard. The most general way I can think of is using the rational root theorem and plugging a few values in.
* - You can factor using ultraradicals (yes, it's a thing), but that is far above highschoolers or undergrads, even.
http://en.wikipedia.org/wiki/Irreducible_polynomial#Real_and...
I'm a computer scientist, one of the more mathematical occupations.
I've never been in a life-or-death situation where I thought, "aha, thank God I memorized that formula in high school!". Also, I don't actually remember it anymore, other than "negative b plus or minus the square root of b squared minus four-a-c, all over two-a".
Well huh. I guess I do remember it, but apparently at a verbal-auditory level rather than visual-symbolic. As usual for me.
Still: I've never had occasion to use that recitation I just made.
2. Have you ever been in a life-or-death situation where anything you learned in class in high school was useful to you? "Well, I would have died, but then I remembered that Julius Caesar's last three words were not actually 'Et tu, Brute!' according to Shakespeare..."
I read/write slow and I have an incredibly hard time memorizing anything so I rebelled. Even after I got my act together, got my GED, and went to college I suffered through the various levels of Calculus because it was the same tune all over again. Classes like Linear Algebra were a lot harder for me to "see" but it was still faster & easier for me to take the time to visualize it.
When I went over it with him, I showed him several spots where he made careless mistakes - he added where he should have subtracted, he multiplied where he should have divided, he screwed up a decimal point, whatever. I told him, "It's easy to spot your errors now because these are easy problems. But when you get to harder math, it's going to be much harder to find out what you did wrong, and a teacher isn't going know whether you made a careless mistake or just don't know it at all. By showing your work, you show the teacher that you actually know it."
Nowadays he understands the reason why he needs to show his work but still hates it. I'm hoping that he'll be like this only while the math is easy.
If you could be given a magical amulet that let you teach students better, more quickly, and more permanently than ever before but at the expense of never being able to test them to see exactly what it was that they learned, or you could be given a magical apparatus that let you test them perfectly so that you knew exactly what it was that they learned and did not learn but gave no insights or help into how to teach them those things that they failed at, which would you choose?
Which would your local school administrator choose? Which would your children's teachers choose? Which would the legislator writing education policy choose?
Everything else is post hoc rationalization. Having decided what it is that we want public education to be, we need to have some sort of justification for it even if it doesn't make sense.
Do you know what people who don't show work do when they move on to more difficult problems? They start scribbling it out on paper, without any prompting. The more difficult problems are interesting enough that they want to get them right, and when they notice that basic mistakes are interfering they strive to avoid those.
Or, in some cases, they just don't bother. When you solve the Poincaire Conjecture (spelling? didn't want to cheat and look it up) no one gives a crap whether or not you "showed your work" because most of the other mathematicians can also "just see" the boring details, and are interested primarily in the truly insightful portion of the proof.
I suspect that we're actually selecting for accountants and not math geniuses when we harp on "showing your work". How many Perelmans did we discourage and how many math stooges were praised last year in public schools?
Meanwhile, if he shows that he's factoring the polynomial and writes a 5 where he should have written a 3, I can immediately tell that he knows what's going on but made a careless mistake. Alternatively, if he writes down a bunch of gibberish, it means that he doesn't know what's going on and needs someone to go over the concepts again.
It's like a compiler. Do you want a compiler that compiles really, really fast but just throws opaque error exceptions, or do you want a compiler that is slower but gives you detailed warnings and error messages? I'd rather take the latter. Maybe once I'm perfectly sure that my code works, I'll do it with the former.
The correct (though inefficient) approach is to keep trying until you see that he starts understanding. However, this is impossible when there are 25 other students in the classroom. Each might require a different manner of teaching to "get it", or learn at different speeds. And so if you're trying to crank out graduates on an assembly line this just won't cut it.
So instead of figuring out a solution where each student can get the education he deserves as a human being, we instead seek to change the student so that he can be programmed with the education that is possible in an assembly line system. This also explains the dearth of highly competent, highly respected teachers... you don't staff your factory with gifted artisans who could carve the pieces. You want someone who will push the button and have the product stamped out in 0.75 seconds.
If you calibrate everything perfectly, some number of students will get a highly optimal (for them) education where everything was timed perfectly, using the easiest-to-understand lessons. For everyone else, for the slow and learning disabled, for the quick and talented... it will be an awful experience. And, whether you call it luck or circumstance, neither of those groups will be educated well enough to be able to express their criticism easily.
> It's like a compiler. Do you want a compiler that compiles really, really fast but just throws opaque error exceptions,
But a compiler isn't a person, and a person isn't a compiler. I don't want to treat people as if they were machines... I especially don't want to treat children like they are machines, it's almost certainly even more damaging the earlier that happens to them.
I'm a programmer too, I do this for a living. I know all too well how easy it is to think of human circumstances and other people as if they were machines to be debugged, and it feels awful. Imagine what the 7 year old kid feels like in school when he's a bug to be solved on the teacher's trouble ticket system. Especially when he's probably marked "low priority, fix when time allows".
You're no longer talking about a system where learning is considered the primary goal. It may not even be a goal at all.
This is a really good point - the public education system isn't an artisanal workshop; it's a large, industrialized factory where "raw materials" are turned into "product." Every grade is another step in the factory process. And while I guess it might be optimal given the very limited resources that we devote to education, it's heartless and doesn't work very well from an absolute standpoint.
Personally, I didn't get a lot of my education from school. Sure, I was there ten hours a day, but I mostly learned from my father and the homework that I did. I would get assignments, and my father was the one who really taught me whenever I ran into problems. I would then go back to school and pass tests.
Unfortunately, my situation was atypical and very lucky; I was blessed with a loving father who was fascinated with a large variety of topics and loved teaching. Most kids don't get a resource like that and get stuck with school as being the only avenue for learning. How can you reach them? I think the only answer is more money, which will go toward more teachers. Cut down the class size to ten kids per class, and you'll get a much more individualized curriculum. As long as you have 25 kids in the classroom, you're going to end up with the factory approach.
The point of showing the work is to learn the mechanics of solving the problem. If you do not learn the mechanics of solving for simple problems, you will not be able to apply the mechanics to more complex problems where one can no longer intuitively see the answer.
I totally get it and it makes total sense except for when it doesn't. The problem with our education system is that it's fundamentally flawed. It is designed to work best with the typical student being taught from a skill set chosen for optimal widget-making. People learn/think differently and yet we cater more and more to the mantra of pump-and-dump where children with the ability to retain the most frivolous information wins.
It took until my junior year as a comp-sci student for me to figure out what I personally needed to learn the material. I absolutely had to understand the big picture before I could ever attempt to solve the problems. If I didn't and I relied entirely on memorization then I was destined to fail.
In order for me to understand the big picture, I had to ask questions, sometimes a lot of them. Abstract questions would annoy some professors and certainly other students. Engineering classes, like most college classes, are full of people brought up in a system where the slide-show-after-slide-show of formulas, facts, or bullet points was all they needed. My questions were irrelevant and an interruption to their note taking.
1) You need to be able to do basic calculations before you can do advanced proofs. I taught a lot of high school seniors, and I had a ton of students who were smart enough to handle abstract concepts, but couldn't follow along when I showed them cool proofs because they got caught up on the basic calculations (because they hadn't learned them well in middle/high school).
2) Good high school teachers DO do a lot of pattern recognition/abstract reasoning. That's the entire idea behind a discovery lesson and constructivist teaching - having students learn formulas by discovering patterns and reasoning about them.
3) Again, as he points out, American high schools do do proofs in Geometry. He thinks they're really pedantic, but there are good reasons why 2-column proofs are so tedious. For one, students seeing proofs for the first time freak out, so giving them structure helps. For another, if the students write out every single step, it's easier to identify who really knows his/her stuff and who's BSing.