I'd disagree on the myth part. I would probably agree with it being likely there isn't a lot of data. Much of the learning styles stuff was put forth by Felde

I'd disagree on the myth part. I would probably agree with it being likely there isn't a lot of data. Much of the learning styles stuff was put forth by Felder at NCSU Engineering (my alma mater). Is there a double-blind study? IDK, but it's interesting, and it resonated. In the informal quiz in my intro to engineering class (Dr. Richard Porter's, not Felder's), it was interesting to see how preferred learning styles (from his quiz) lined up with majors. In short, mostly it was that a large number of people had visual vs written preferences, but the one thing different for C.S. students were they almost always learned globally (i.e. almost random access, not really understanding the whole, and things then popping into place as connections build up between ideas) whereas other majors preferred seeing things step by step always building on one another. It resonated with me in general because I'm generally lost with something until I accumulate a lot of random concepts enough to get it. http://www4.ncsu.edu/unity/lockers/users/f/felder/public/Papers/Education_Papers-Chronological.html http://www4.ncsu.edu/unity/lockers/users/f/felder/public/Pap... I think it's great people are trying to pay attention to way s people learn and how to present information. This hit home really hard when doing docs for ansible - and I tried to present things in multiple ways (different ways of indexing, presenting big picture versus building things up, and vice versa) and in writing technical documentation and seeing bugs on understanding (and twitter complaints) on tech docs it is clear people DO learn very different on the sequential vs global axis. I also really DO need diagrams, as large volumes of words get my lost, but strangely I produce large volumes of words and seldom any diagrams. I'm also strange in that if I take notes, I almost never read them myself, so this is perhaps why I'm so bad about learning from written text and always want to jump into code snippets. (Novels, sure, they are great). I also usually need a whiteboard as a buffer for understanding architectures visually, where I notice a lot of people don't need to draw things out, or it doesn't help them (or aren't as interested in those things?) It's useful to present things in different ways and mix things up -- not that you have to repeat everything 4 different ways. That was what Felder was trying to get across. (A simple example might be it is good to present a diagram next to a paragraph describing a concept.)