|
I'm a mapper [1], and as such, I tended to seek out information that matches some edge of what I know, and when I find it, I'm then able to incorporate that knowledge, and check for inconsistencies with the other fact I know. I just keep reading, and browsing until I find the right puzzle piece, and then I understand. I like instructions that specify how things work, so I can route around problems, and understand what the goals and mechanisms of a system I'm using. I can tolerate a wide variety of discrepancies in those instructions, and work around small changes in procedures that might not be documented. If I'm being tested on general knowledge, and how things work, it is stuffiest to read and understand the materials provided. Practical Example - Right now I'm trying to understand the fine grained details of how quantum computers work, I've watched a lot of boring youtube with words like Hamiltonian, Eigenstate, etc... none of which has clicked, but all float around like loose puzzle pieces... eventually I'll find the detail I need, and a connection will be made, I'll then go back and find other pieces until I understand the landscape at the detail I want to know. If I'm being tested on random facts (dates, buzzwords, etc) then it's time to break out repetition and wrote learning. This is also the mode when learning a new skill, practice, practice, practice. --- If you're a packer, the opposite is true. You'll likely keep a lot of notes, and be good at memorizing facts. I've worked with packers in the past, they like clear, precise, easy to follow instructions that very closely fit what they will see as they follow them. If the instructions don't match what they see, they will end up needing help, or get frustrated. I'm not sure how packers best learn. I suspect it's repetition all the way. --- 1 - https://wiki.c2.com/?MappersVsPackers |
Repetition of the same problem type or set can give illusion of fluency through short term memory familiarity.