I have to disagree to the basic assumption of the article. Its often not necessary for a coder to understand why math works, but only how to use their results.

I have to disagree to the basic assumption of the article. Its often not necessary for a coder to understand why math works, but only how to use their results. e.g.: I've coded fft in 5 different languages, and used it uncountable times. Still it took ages to understand why dft works, and I did not yet took the step to understand how dft leads to fft. I know dozens of Second Life scripters (including me) who use quarternions regular, still nobody could tell me, why they work so good for 3d rotations. I've coded my first Markov, 35 years ago, at the age of 12, and Markov was never mentioned in school at all. I'm using dozens of machine learning methods on daily base, coded a few my self, but I do not care to know why they work, but only what their strong points and limitations are. Its not necessary to know how to design and build a car, if you just need to drive from A to B. Its not necessary to study bio-chemistry, to be a good cook.