To the brain, reading computer code is not the same as reading language
1–10 of 232 posts
Re: To the brain, reading computer code is not the same as reading language
#2But seriously, by recalling and introspecting the thought process occurred just before an interruption, I think coding is moke akin to navigating a landscape -- it has a substantial spatial component.
Simply put, it's like thinking about consequences and dependencies at every given line/statement. Something that we don't do (or do rarely) while speaking or reading.
Re: To the brain, reading computer code is not the same as reading language
#3Re: To the brain, reading computer code is not the same as reading language
#4Re: To the brain, reading computer code is not the same as reading language
#5Re: To the brain, reading computer code is not the same as reading language
#6A lot of the time editing, I'm not really paying attention to the meaning of what's written, but whether the meaning is conveyed properly and clearly in any given sentence or paragraph.
Re: To the brain, reading computer code is not the same as reading language
#7Re: To the brain, reading computer code is not the same as reading language
#8[0]: http://web.mit.edu/9.s915/www/classes/duncan.pdf [1]: https://i.imgur.com/xdYzbev.png
Re: To the brain, reading computer code is not the same as reading language
#9Re: To the brain, reading computer code is not the same as reading language
#10It was interesting to read. There aren't many google results for 'multiple demand network' that I could easily parse, but I did happen to find this paper on it in primates[0] (also happens to be from MIT) when I was trying to find an image that showed what parts of it are activated. I found this slide from a lecture very interesting[1]. [0]: http://web.mit.edu/9.s915/www/classes/duncan.pdf [1]: https://i.imgur.com/xd…