Skip to main content

Teaching Math

I recently bought myself a Math book that I'm delighted with (Mathematics 1001 by Elwes). I'm finally understanding many math concepts I had not understood in my education and I've reached an few interesting theories on how math should be taught.

There should be three things that a math class should teach at the same time:
1. Memorization
2. Visual (Graph-Based)
3. Procedural (Equation-Based)
4. Historical

All four are part of a whole and some students will respond better on one than the other. These are four avenues to teach the same thing by the way not three different things.

Memorization should begin really early. There is no need to explain how multiplication works to have the kids start to memorize the multiplication table. The reason is not that you *need* to memorize it but  that by doing so or encouraging kids to do so, they'll be faster at doing calculations. Here are the things I think should be memorized in math:
a. all the pairs of numbers that add up to 10.
b. the first 32 square roots.
c. the multiplication tables up to 12 for 3, 4, 7, 8 and 12, because these are the trickiest ones.
d. the prime numbers with 1 or 2 digits.
e. the Sine, Cosine triangle calculations.

Of those I only memorized the first and the last, but he key here isn't to force the kids to all memorize them but to encourage them to.

Visual (Graph-based) math is my favorite and I have a natural proclivity for it. I did extremely well in geometry, but graph based math allowed me to understand calculous. To this day when I do a limit, I visualize the graph in my mind. It is my theory that some people have a more visual mind that process math better graphically than procedurally (equation-based).

Procedural (Equation-based) seems to be the physics way to teach math. Everything gets boiled down to an equation. Some people need to visualize the relationship between numbers while others find the visual clutter, well, cluttering. Some crave a purely mathematical description of the relationship, because it creates the relationship instantly. It's like sight reading code. I can describe a pattern with words and leave you confused but the code, is unambiguous. And some people really enjoy equations that way. There is a beauty in the sparseness of an equation that is undeniable.

Historical perspective has helped me understand some of the more basic concepts of math that seem just weird. For example what are rational numbers? Or really who cares about them? Really? We live in a world of real numbers so the previous historical divisions of numbers don't necessarily map well to the reality of today. A historical perspective can help. Once I understood the strange almost spiritual fascination the Greeks had for integers, suddenly rational numbers made more sense. Considering most numbers we encounter today are real numbers and not integers it can be confusing to go from rare numbers (integers) to rarer (rational) to not-really used  in real life (irrational) to the most common (real) numbers in number theory.


Popular posts from this blog

How to configure Ubuntu's keyboard to work like a Mac's

Typing accents on a PC is a complicated Alt + three numbered code affair. One feels like a sorcerer casting a spell. "I summon thee accented é! I press the weird magical key Alt, and with 0191 get the flipped question mark!" For a bilingual person this meant that writing on the computer was a start-and-stop process. With Mac's it a whole lot easier, just Alt + e and the letter you wanted for accents and alt + ? for the question mark. No need to leave the keyboard for the number pad and no need to remember arcane number combinations or have a paper cheat sheet next to the keyboard, as I've seen in virtually every secretaries computer in Puerto Rico.

Linux has a interesting approach to foreign language characters: using a compose key. You hit this key which I typically map to Caps Lock and ' and the letter you want and voilá you get the accent. Kinda makes sense: single quotation mark is an accent, double gets you the ümalaut, works pretty well. Except for the ñ, wh…

Contrasting Styles of Writing: English vs. Spanish

There is interestingly enough a big difference between what's considered good writing in Spanish and English. V.S. Naipul winner of the 2001 Nobel prize for literature publish an article on writing. In it he emphasizes the use of short clear sentences and encourages the lack of adjectives and adverbs. Essentially he pushes the writer to abandon florid language and master spartan communication. This is a desired feature of English prose, where short clipped sentences are the norm and seamlessly flow into a paragraph. In English prose the paragraph is the unit the writer cares about the most.

This is not the case in Spanish where whole short stories (I'm thinking this was Gabriel Garcia Marquez but maybe it was Cortázar) are written in one sentence. Something so difficult to do in English that the expert translator could best manage to encapsulate the tale in two sentences. The florid language is what is considered good writing in Spanish but unfortunately this has lead to what …

Fixing Autocomplete in Github's Atom Text Editor for Ruby

I really like Github's Atom Text Editor. I really like that it's multi-platform allowing me to master one set of skills that is transferable to all platforms and all machines. 

On thing that just burns me of the default set-up in Atom is the Autocomplete feature that seems to change my words as a type them. Because Ruby uses the end of line as a terminus for a statement you usually finish a word with pressing the return button and you get really annoying changes to your finished typed word a la MS Word. I find myself yelling "No that's not what I wrote!" at the screen in busy coffee shops.

I disabled autocomplete for a while but it is a very useful function. Then I found out they changed the package that gave the autocomplete to a new one called "Autocomplete Plus" that gives you more options. All that I needed to change to make autocomplete sane again:

1. Open Atom's Preferences
2. Search the bundled packages for "Autocomplete Plus"

3. Go to t…