I want to ask you about what is probably (judging from, among other things, the reviews on
Amazon) the most divisive introductory text in the field:
Structure and Interpretation of Computer Programs.
(And if you haven't read it before, take a look at the
online edition. It will be well worth your time - if it doesn't put you to sleep, that is.)
It's an odd little book, and tends to generate strong emotions. I am personally in love with it, and with the Scheme language, but I've got a definite theoretical bent; and even given this, the rather abstruse nature of the text makes it hard to follow, and even harder to apply to real world programming (I discuss this in greater depth
here and
here). Practical-minded programmers almost universally hate it, because it is entirely abstract - it takes a lot of effort and time to digest the material, and even then, the presentation is so dry that a lot of programmers find it completely worthless. Even on an abstract level, many have opined that it is sloppy and poorly thought out, but others aver that it is lucid and tightly-reasoned. There doesn't seem to be much room for compromise with it - for most people, they either love it or hate it.
I was wondering what the folks here thought of it. Any comments?
(This has been crossposted to the
NightStar Code Monkeys forum and
User Friendly ARS, if you are interested in seeing the responses from elsewhere.)
_________________
Schol-R-LEA;2 ELF JAM LCF BiWM MGT GS
First Speaker, Last Eristic Church of Finagle and Holy Bisexuality
#define KINSEY (rand() % 7) // Keeper of the
Tent Peg of Homosexuality +5You draw it, we misinterpret it. - Bo Lindbergh // Realitas vestri renuo, sufficioque mei.
"Fundamentalism, not atheism, is the ultimate rejection of faith."