6 ms·
I'm largely of the opposite group. Having names that aren't pronounceable helps me read code faster, as I don't try to pronounce it, and can just treat the enti
by stordoff 8y ago
I'm largely of the opposite group. Having names that aren't pronounceable helps me read code faster, as I don't try to pronounce it, and can just treat the entire word as a unit rather trying to "read" it.
I do the same in English when reading fast. I distinctly remember reading "Hermione" in Harry Potter as a child, and, because it was a name I hadn't encountered before, just "reading over" it and not thinking about the actual pronunciation. I didn't think about the actual pronunciation until some years later (probably when it was brought up in the books). Even now, if I try to pay attention to my internal monologue whilst reading, it's often words running into each other or being skipped, unless I deliberately slow down, because I'm not actively subvocalising and I'm reading faster than I would pronounce them.
- rectang 8y agoThat makes sense. Then the question in the context of "learning styles" is, if these differences are real, are they actionable -- can we produce measurable differences in outcomes?
- itronitron 8y agothat reminds me of reading Huckleberry Finn and having no idea what Jim was referring to when he used the word 'chile' until I actually sounded it out and then everything Jim was saying made sense
- Kluny 8y agoHermy-own. I stumbled on it every single time.