This is all well and good, until the day when you decide to learn something on your own from a book, and encounter concepts defined in epsilon-delta form that make zero sense to a mind trained on intuiting concepts from graphs.
Visualization will not get you beyond 3 dimensions, nor will it get you understanding systems in terms of Lagrangians/Hamiltonians, nor will it give you the ability to read texts geared toward actual mathematicians.
Speaking for myself, it was surprisingly difficult un-learning the "slope of a tangent line" type of conceptualizing in order to understand math with sufficient rigor to be able to actually read math texts correctly.
Understanding by symbol pushing is not real understanding. This is all that is wrong with how mathematics in college is taught. They start and end with symbol pushing, and the real insight remains locked in the professor's head. The professor projects his insight into symbols, and the students only learn the projection.
What should be done is start with the intuition and visualization, and then show how the ideas can be made precise. If you would have been taught only the epsilon-delta form from the start, it would have been easy precisely because you would not yet have obtained the real understanding.
Even in high dimensional spaces visualization is very important. This often happens by analogy with lower dimensional spaces. For example if you start with a region in Hamiltonian phase space, then the region's volume is constant as time evolves. This is a highly intuitive and visual statement. Saying the same in symbols wouldn't be nearly as clear.
Yes, the "develop a visual analog" approach will not be effective if you spend all your time translating back and forth between the linguistic abstraction (for all delta, there is a small enough epsilon such that...) and your visual analog. For example, I just checked, and Baby Rudin (http://www.amazon.com/Principles-Mathematical-Analysis-Third... ) does not contain a single picture or line drawing.
Additionally, some things like ordinary algebraic manipulation are very well-suited to linguistic abstractions ("multiply the polynomials, take the derivative, put all terms involving z on one side of the equation, apply the quadratic formula"). Sometimes only the linguistic abstraction can give the solution (e.g., "this problem is easy because the quadratic coefficient cancels out, and the equation is in the form t^3 + c t = d").
It's also worth noting that manipulating the linguistic abstractions takes a lot of insight and talent (e.g., knowing the perfect substitution of variable to make an integral fall into a known form, or knowing which one of the four error terms will be hard to control, and working on it first).
It's not wise to be over-committed to the visual approach.
I have generally found it very helpful to spend a lot of time understanding the behavior simple concrete cases, and understanding how a general mathematical principle applies to them. The visualizable low-dimensional case of analytic geometry is a particularly flexible concrete case for understanding many principles of calculus and linear algebra. I appreciate fairly well how it breaks down: I went on to path integrals and other quantum stuff where the number of dimensions is much larger than three. But the understanding from 1-3 dimensions was very helpful. More generally, one can make a habit of thinking about how general principles apply to special concrete cases that you understand. When trying to understand group theoretical theorems, you can check how they apply to your favorite concrete groups. When trying to understand conservation of angular momentum, or the Bohr correspondence principle, you can cross-check your understanding of them with what you know about the behavior of hydrogen atoms and balls rolling off the edges of tables and so forth. And probably many readers here will have naturally tried thinking about how a nontrivial algorithm would work on some simple concrete data set.
The advantages of thinking this way seem to be a little like the advantages of test-driven development: time spent understanding representative concrete cases doesn't teach you everything, but it can eliminate many misunderstandings very quickly.
The important part is understanding the concept.. not to necessarily visualize it. For instance, once you understand the concept in 1D, it's not that much more difficult to extrapolate to multiple dimensions.
In my experience, it’s the transition from 1d to 2d that’s the most important. You learn the concept in 1d, then carefully transition to 2d while still keeping an eye on the 1d case and on what the extra dimension contributes. The understanding of the latter helps to get from n to n+1.
Visualization will not get you beyond 3 dimensions, nor will it get you understanding systems in terms of Lagrangians/Hamiltonians, nor will it give you the ability to read texts geared toward actual mathematicians.
Speaking for myself, it was surprisingly difficult un-learning the "slope of a tangent line" type of conceptualizing in order to understand math with sufficient rigor to be able to actually read math texts correctly.