Callista wrote:
That, and depending on an IQ test to tell you whether you're smart is kind of silly anyhow. Just spending time in school, learning and solving problems, will raise anybody's IQ score. Innate talent makes learning easier--but the actual learning the skill has to be done through practice, and the skills you use on IQ tests are no different.
This idea that IQ is unchangeable and you're born with it... it's silly. It's as though we didn't learn from our early environments, as though our brains didn't adjust themselves to the things that we require them to do in our particular cultures.
Give me the right training, and I'm pretty sure I could learn to ceiling out any IQ test you pleased. And that's not because I'd be smarter somehow; it'd be because I'd have practiced.
When I was working on hacking Super Mario Bros. 3, I also hacked the machine code. I would write out the instructions in 6502 assembly, and then using a guide to convert the instructions to the correct machine code op codes, namely the "6502 Instruction Summary," which can be found here:
http://nesdev.com/
I printed the TXT file out, and for every instruction I would refer to the printed copy. Only for a few addressing modes of LDA (load value into accumulator) and STA (store value in accumulator in location in memory) and I think maybe also JMP (jump to address) and JSR (jump to subroutine, which when you reach RTS you go back where you were) did I ever trust my memory. (I did not want to make a mistake and use the wrong op code as that could have created a hard-to-find error.) So it was thorough back and forth checking as I entered each instruction into the Hex Editor I was using (XVI32). I thought I became rather good at it. On the surface it looks grueling, but I actually had a lot of fun doing it.
How is this relevant? This task seems to be similar to Digit-Symbol Coding, where the instruction name and addressing mode served as the digit and the op code served as the symbol (what it needs to be coded as), while of coursing making sure 16-bit addressing mode was done in little-endian order (least significant byte goes first).
So maybe my Coding score will be better than it was in the past from all this learning (where I scored a 5 at 8 and an 8 at 15)? Perhaps even above average? One thing I noticed while testing, and maybe the examiner did too, was that I did not memorize any of the digit-symbol correspondences, but would for every single entry look up at the key and then back down to the box I was at. That might have slowed me down, but it was a habit that may have been built from my manual assembling, or maybe I was always like that.
I proctored my mum on a related test, the Symbol-Digit Modalities Test (which is where you put in the digit instead of the symbol), and she remarked to me that same mistrust and disregard of her memory, so maybe it's inherited.
_________________
"You have a responsibility to consider all sides of a problem and a responsibility to make a judgment and a responsibility to care for all involved." --Ian Danskin