>>10
The interesting part is the depth of the treatment of each topic, and the general attitude towards problem solving and mastery of the field.
But as a C programmer, you should start from chapter one, as it will introduce you to functional programming, from which it will veer off near the end of chapter two (which deals with data abstraction, so it's more worthy of skimming through it), to start chapter three with the introduction of mutable state, its representation, consequences and organization (they introduce constraints-based programming and laziness there too).
I haven't yet reached chapter four, but they turn to languages in it, and in chapter five to machines and compilation.