Spatial Ability a Predictor of Creativity In Science 199
HonorPoncaCityDotCom writes "The gift for spatial reasoning — the kind that may inspire an imaginative child to dismantle a clock or the family refrigerator — is sometimes referred to as the 'orphan ability' for its tendency to go undetected. Now Douglas Quenqua reports that according to a study published in the journal Psychological Science, spatial ability may be a greater predictor of future creativity or innovation than math or verbal skills, particularly in math, science and related fields. 'Evidence has been mounting over several decades that spatial ability gives us something that we don't capture with traditional measures (PDF) used in educational selection,' says David Lubinski, the lead author of the study and a psychologist at Vanderbilt. 'We could be losing some modern-day Edisons and Fords.' Spatial ability can be best defined as the ability to 'generate, retain, retrieve, and transform well-structured visual images.' Some examples of great inventors who have used their high levels of spatial ability to innovate include James Watt, who is known for improving the steam engine, and James Watson, co-discoverer of the structure of DNA. Nikola Tesla, who provided the basis for alternating current (AC) power systems, is said (or fabled) to have been able to visualize an entire working engine in his mind and be able to test each part over time to see what would break first. Testing spatial aptitude is not particularly difficult but is simply not part of standardized testing because it is considered a cognitive function — the realm of I.Q. and intelligence tests — and is not typically a skill taught in school. 'It's not like math or English, it's not part of an academic curriculum,' says Dr. David Geary. 'It's more of a basic competence. For that reason it just wasn't on people's minds when developing these tests.'"
Re:Wow this is the best handwaving I've seen in a (Score:4, Insightful)
You can easily measure them. Getting people to agree on what the measurements mean in practical terms is where we fail.
Re:Wow this is the best handwaving I've seen in a (Score:4, Insightful)
Re:OK, we get it (Score:5, Insightful)
Wrong. The master skill is laziness. The desire to automate everything so you can sit back and read a good book or use spacial abilities to hack on your home automation Arduino kit, so you can sit back and read a good book.
Re:I predict (Score:2, Insightful)
It's like (motor vehicle) driving skills. Everybody thinks they're above average.
The big question (Score:5, Insightful)
Is good spatial ability because of / or an indicator of creativity?
Or, is creativity because of good spatial ability?
If spatial ability has some sort of causal effect on creativity then LEGOs (and no, I don't work for them! :) should be required part of every childhood. (How many science Nobel prize winners used LEGOs/tinker toys/wooden blocks when they were little?).
Also it would be an interesting to see what effect watching movies or even playing video games have had (looking at images on a 2D surface) have had. Maybe that explains the term "couch potatoes" (looking at 2D images exclusively might make the brain very UN-creative). Perhaps 3D video games like FPS would more than make up for this and games like minecraft even more so. Still this is another reason why fully immersive virtual reality can't come soon enough (that is if we don't all get sick from vertigo)!
I wonder if the stock price if LEGO has changed due to the findings from this study?
Re:I predict (Score:4, Insightful)
It's like (motor vehicle) driving skills. Everybody thinks they're above average.
And if you take a survey are an F1 drivers meeting, they may be correct.
Re:Wow this is the best handwaving I've seen in a (Score:5, Insightful)
The only answer is Nunchucks.
Re:Wow this is the best handwaving I've seen in a (Score:4, Insightful)
A. Creativity cannot be taught.
While true, ...
Says who? Creativity can and is taught. I teach it all the time. I work with kids in after school programs. We do science and robotics stuff. I have taught the kids to better visualize moving 3D parts by practice and exercises. I have also taught them how to come up with creative ideas. There plenty of ways to do this. If you pair a dull kid up with a brighter kid, he will learn by example. I teach the kids that, instead of starting with a conventional solution and working forward to something innovative, do it the other way around: think of the craziest thing you can, and then work backwards toward something that is actually workable.
Re:'Bell Curve' has been debunked (Score:5, Insightful)
Or to make it more explicit: IQ is especially scaled and scored to ensure the distribution of the scores is gaussian.
Re:Wow this is the best handwaving I've seen in a (Score:4, Insightful)
Competent programmers are a dime a dozen.
Programming is the easiest damn thing in the world. It's so easy that children can and do easily teach themselves!
Sure, some problems are hard. Luckily, you can sometimes avoid them altogether. Go read some of Chuck Moore's work.
Anyhow, how do you judge the quality of a programmer? There's only one way that I know: by the quality of their output. But that can't be right, can it? Some of the most incompetent code I've ever seen has been written by programmers generally considered to be brilliant.
Take a chunk of code known to work correctly. It won't take you long to find one developer to say that it's brilliant, and another to say that it's total garbage. Why? The first developer either doesn't understand it or sees some clever or interesting tricks. The second developer sees it as unnecessarily complicated, the same problem being solvable with a much smaller, faster, and simpler solution.
If you'd rather: Perhaps the code is fine and solves the problem well, but the second developer would have approached the problem differently. Maybe they disliked the use of a specific language feature [oracle.com] or technique, choice of brace style, or selected language.
Programmers usually aren't well versed in the humanities and tend to think in absurd black-and-white terms. They constantly mistake completely subjective judgments for objective conclusions. They're also prone to believe absurd myths (mistaking common wisdom for objective fact) and tend to buy in to the latest industry fads. You'll frequently find them defending statements that they obviously don't understand. They've simply never questioned their favorite meme. How could it be anything other than pure fact? Programming is like math, right?
Code quality is highly subjective, obviously. I understand that there are objective metrics like size, speed, and memory use. However, we can only use those to compare two solutions to the same problem! Even then, subjective measures (like readability) will quickly come in to play, which some people will consider to trump this or that objective measure -- particularly when two solutions are close on objective terms.
That absurd black-and-white / right-wrong thinking makes each person think that their subjective opinion is objectively correct, and thus irrefutable. What else can they assume but that they're surrounded by incompetent morons?
Do you know who writes bad code? Everyone. The best developer you know wrote crap code last week. You wrote crap code last week. I wrote crap code last week. Not you, you say? You used the latest set of buzzwords? Remember this: Yesterdays best-practices are today's obvious mistakes. Sometimes they oscillate between bad and good. Pick damn near any topic and dig through both current and old articles and blogs to get a sense of how the common wisdom changed over time. (Nonsense "design patterns" are an easy mark. You'll find lots of back and forth on many of those.)
There are other reasons, of course. A big problem seems to be developers over-complicating problems. Sometimes going so far as to write an interesting problem that solves the problem they've been tasked with as a side-benefit. I replaced an 81k (1700 line) component with an 8k (300 line) component a couple weeks ago. Was the developer of the old component incompetent? Not at all. He just made the problem significantly harder than it was. I'd guess that it was to keep the otherwise dull project interesting -- or because he found the problem space interesting and wanted to explore it.
When I see stuff like this I can't tell if it's arrogance or just insecurity.
Re:Wow this is the best handwaving I've seen in a (Score:5, Insightful)
And who brings on the brighter kid, handicapped by his dull team-member ?