??? This has to be one of the most misinformed and strangest posts I have read here.
I don't think you have any idea of what quantitative finance requires, and you are completely wrong on almost all counts.
Firstly, it used to be the case that Quants came from Maths, Physics (particularly astro and particle physics) and Engineering (Control and DSP), but this is no longer the case. These days there exist excellent programs in Mathematical Finance and Financial Engineering, as well as that many modern finance courses have a substantial mathematical content available to students. The Chicago course with Steve Shreve comes to mind.
Secondly, and although linear algebra is a significantly important aspect of quantitative analysis, it is not 100% of the mathematical skillset needed by quants, as your post appears to imply. Some might say that modern mathematical probability is more important, others might say partial differential equations are. I have worked with quants whose PhD's were in Group or Number Theory, not really applied stuff, so a varied lot. These days we are seeing more come from specialized graduate finance courses with good math stat and coding skills.
Thirdly, and I believe I know the posts you are alluding to, I don't see where any one said that programming is not necessary to do the work of a quant. Most quants are quite proficient in C++, Matlab, Mathematica,VBA, Excel, Gauss - depends on where and what you work on. What a quant does not need, which I believe was the idea conveyed in the post, is extensive knowledge of the dustier corners of C++. There's no need for that. Having encyclopedic knowledge of really obscure C++ does not mean you can code. I have seen many examples of this, and this is normally a terrible interviewing tactic. Any good quant who can code should have a good knowledge of sound software engineering principles and apply them to write fast, efficient and robust code. This is tough to do if you are a FO quant and you have a trader yelling at you to get the job done like yesterday! Some interviewers might ask you to code a couple of classes and price something - fairly basic stuff. These are the good ones. The bad ones will ask you very specific dusty corner C++ questions - this is utter rubbish. If you get that in an interview, then get up and run. its probably a second rate place and not good to work in. This has been my experience. When I was interviewing potential candidates a few years back, I changed the C++ questions. No longer would we ask rubbish like bitfield structures in C++ (which is straight C anyway) and trick questions like what is a virtual constructor (there is none, this is the stupid name sometimes given to the factory method pattern), etc, etc. Actually asking deceptively simple questions allowed me to gain significant insight whether the person had textbook knowledge, some experience, or significant experience and sound software engineering skills.
HTH.