How'd you read your code?

How'd you read your code?. The /. article got various responses:

• some simply don't read their code (think of shell scripters),
• some go with high-level tech-like abstraction,
• some go with word by word substitution to daily words, mostly English,
• some read the each symbol and token of the code,
• some got angry/sentimental/high when reading a piece of code they wrote themselves previously,
• some got into their zen analytic mental concept.

The problem is largely how to translate analytic construct to communicative linguistic construct.

Programmer/engineer/code usually have easier time with charts and graphs. Still, programs' linguistic construct is also important in conveying how the things should be used (not how it works) and explaining to new-programmers, like from lecturer to students (or you to your SO, if it matters).

I'd suggest explaining the arithmetic-logic process with natural language, one block (lines of code delivering particular function) at a time, somewhat in between between usage-and-purpose-driven and value-and-function-driven. Hopefully we can actually learn how the the code works, what purpose lies beneath, and what to alter/modify/add in the code to suit one's specific usage scenario.