quote:it. But just like you can visualize audiobooks just as well (and sometimes better) as when you are reading, the same applies to programming.
Books, whether they be written or spoken, are linear. The story might not be, but the book is -- you read the first word, then the second, then the third, on until the end. It lends itself very well to audio.
But code is not that way at all. All but the simplest programs have branchings, loopings, and jumps that would be extremely hard to comprehend in a linear medium such as audio book.
I realize this, the audiobook this is just an analogy. I'm saying when you take away your sight, you might improve your memory enough (as well as become much more detailed in your commenting) to compensate for this. Like, every time the program calls up a function in a different part of the code, leave a comment "segment located on lines 863-895" or something. I don't know... I know it'd be a lot less convenient, but I think it'd just take some discipline and practice.
Posts: 2222 | Registered: Dec 2008
| IP: Logged |
Printer-friendly view of this topic
![[Razz]](tongue.gif)
