Reading code differs fundamentally from reading English text because code is ordered by computational requirements rather than narrative flow, is typically consumed as diffs rather than complete programs, and exhibits far greater structural complexity than literature. The article advocates for non-sequential "dyadic scanning" approaches—multiple passes tracing execution paths and dependencies—rather than front-to-back reading.