Learn Difficult Concepts with the ADEPT Method
betterexplained.com
betterexplained.com
The two things that I found most helpful in relearning math is (1) building up a foundation for mathematical concepts through betterexplained's intuitive method and (2) turning it into code as soon as possible. For the latter, I have a side project that is a sort of platform to test all my various ideas, from city performance modeling, to procedural form generation, where I am constantly trying to rework or tweak with new math formulas. It's amazing how much more efficient and useful this is as a learning method.
The sooner traditional universities and their ineffective, anachronistic teaching practices die out as the main form of tertiary academic education, the better. They could be replaced tomorrow by some combination of recorded lectures given by presenters who are actually good and in-person tuition given by people who can actually teach and care about their students' education, and I suspect absolutely nothing of value would be lost. The students would be both better educated and probably much better off financially, while the academics with a talent for research but not for teaching could make better use of their time and skills.
Apparently, good teaching doesn't require specific talent. It is a learned skill: http://www.economist.com/news/leaders/21700383-what-matters-...
At university in the 1990s I preferred learning from (good) textbooks over most lectures, and today there's the Internet - I've actually gone back to learning with >50 courses on Coursera and edX over the last few years. So I think the problem has shrunk significantly since you can choose to learn from great teachers more easily than ever. But I'm a "pull" person when it comes to learning, meaning I don't even want someone to tell me what I'm supposed to know, I prefer to go out and look and select and get it myself.
Most of those academics could have done with learning about the ADEPT method we're discussing here and similar ideas. Unfortunately, they just had no interest in doing so. As you say, teaching well takes time, but it also takes a willingness to try to teach well.
I remember a particular meeting at the end of an academic year where the teaching representatives of the faculty at my university were seeking feedback from the undergraduate students. When one of the students boldly (but entirely fairly) asked why the presentation skills of most of the lecturers were so bad and why they weren't required to undertake training to improve when the university's teaching so fundamentally depended on them, the reply was essentially "We know and we agree, but they wouldn't accept it." In almost any other profession, the response to substandard performance of a key job function and refusing to undertake measures to improve would be getting fired.
These days, with students here in the UK paying thousands of pounds in fees every year on top of what we used to have, I can't imagine that official response would go down any better than it did for us, but as you say, these days there are more promising alternatives. This is why I think universities need to stop being the main tertiary academic education, at least in anything like their current form.
But I had no mental model on which to hang the various results, and struggled to keep it all in my head, particularly after a break of a few weeks. IIRC, I stopped around the point when eigenvectors are introduced.
Oh, and please share examples of your coding+learning approach :)
My litmus test became: If I can't intuitively describe i^i (an imaginary number to an imaginary power) I don't understand it. I don't care if I can derive the equation 15 different ways. If I couldn't spit out some properties of i^i (positive or negative? Real or imaginary? Big or small?) after a glance then I knew I didn't know it. (Why can I spit out properties of 2^3 or 3^(-4) in a few seconds, but not i^i?)
Code is an excellent way to practice these ideas; the bugs in your logic correspond to the bugs in your thinking, and you see (very explicitly) where to correct them.
This is the model all high school and college students will be taught in 100 years, or perhaps even in 50 years, and it will prevent an enormous amount of confusion and misunderstanding. It’s already becoming the practical tool of choice in many geometric computing problems, and among niche groups of physicists.
”Reforming the Mathematical Language of Physics”, http://geocalc.clas.asu.edu/pdf/OerstedMedalLecture.pdf
“Grassmann’s Vision” http://geocalc.clas.asu.edu/pdf/GrassmannsVision.pdf
“Imaginary Numbers are not Real” http://geometry.mrao.cam.ac.uk/wp-content/uploads/2015/02/Im...
“Geometric Algebra” http://arxiv.org/pdf/1205.5935v1.pdf (this one is a good place to go if you get stuck in another source).
(Or books might be better sources for going in depth. Search for New Foundations for Classical Mechanics, Geometric Algebra for Computer Science, Geometric Algebra for Physicists)
You’d also probably enjoy Hestenes’s work on modeling in physics teaching, e.g. http://modeling.asu.edu/R&E/ModelingThryPhysics.pdf http://worrydream.com/refs/Hestenes%20-%20Modeling%20games%2... http://modeling.asu.edu/R&E/Notes_on_Modeling_Theory.pdf http://modeling.asu.edu/R&E/Hestenes-ModelingTheory2007.pdf
I got through most of math fairly easily by having a mental model of what was going on and could always check that I was on the right track as it made sense in my mental model. However, when I got to Laplace transforms I never figured out how to visual what that meant. Everything collapsed into transform into the magical space where you can do some things easier and then you can transform out into a new place. I could never be sure of how I got from a to b without a tedious examination of every step to ensure I applied the rules correctly.
I'd love to have a mental model for Laplace Transforms.
As a generalization, how does one explain things where no good mental model exists?
Papert et al. are convinced that computers ought to help with this problem. The idea is that visualizations, even if they are interactive, aren't very useful. Instead, the learner should iteratively build and play with a simple version of a model (a microworld) until the learner gets into the full-fledged model. Preferably by programming the model itself.
It's sad that this idea never caught much traction beyond educating children.
Try https://www.khanacademy.org/math/differential-equations/lapl...
The Fourier Transform breaks a signal into its "cycle recipe" (what circular paths are present?). The LaPlace Transform breaks a signal into its "spiral recipe".
Circles are made from a type of exponential (given by e^ix), and spirals are the more general version, where the radius changes (if s=a+bi, then e^is = e^a * e^bi, aka a circular path where the radius changes exponentially).
The LaPlace transform actually deals with decaying spirals (negative s) -- why is this useful?
Well, perfect circles that never decay (the Fourier Transform) are nice for analyzing audio samples, as in music. (Repeated drumbeat throughout the song.)
Decaying spirals model things in the real world, where friction, etc. dampen the signal over time. The Laplace transform can cleanly represent this scenario, whereas you need an infinite number of cancelling terms in the Fourier Transform to represent the "decays over time" setup.
Engineering applications prefer Laplace, compression mechanisms may prefer Fourier. (Separately, Laplace/Fourier make differential equations easier to solve by writing functions in terms of exponentials, which are easy to derive/integrate. The Laplace transform is more general and powerful in this regard, since it can handle any rate of decay, including 0. The Fourier Transform is embedded within the Laplace.)
Just some quick thoughts from an amateur on this :).
Teaching from first principles solely from the technical definition wouldn't be very pleasant for most.
Some of the examples they provide are stories ("Academic progress on imaginary numbers took off only after the diagrams were made!"), but the notion of teaching with a story isn't made explicit in the steps of the method.
Some analogy, visualisations and plain english.
I think I'm going to try explaining git branching/merging to newcomers via interpretative dance in future.
Coming to think of it same for OO. All those silly Dog is an Animal examples spring to mind.
How does it compare to "How to Solve It"?